Analysis of "SQLDIAG.BLG"

Report Generated at: 12/16/2009 4:06:20 PM
PAL

On This Page


Tool Parameters:


NameValue
Analysis of Log: SQLDIAG.BLG
Analysis Interval: 19 second(s)
Threshold File: SQLServer2005.xml
How many processors (physical and virtual) does the server have?2
Was the /3GB switch being used on the server?False
Was the computer 64-bit?False
How much memory did the server have in gigabytes?2
Is the System set to create a MEMORY.DMP file on C: drive in the event of a server crash (blue screen). By default this is set to C: drive.True
Back to the top

Chronological Order


Alerts by Chronological Order

Description: This section displays all of the alerts in chronological order.

Alerts

An alert is generated if any of the thresholds were broken during one of the time intervals analyzed. The background of each of the values represents the highest priority threshold that the value broke. See the each of the counter's respective analysis section for more details about what the threshold means. A white background indicates that the value was not analyzed by any of the thresholds.
Time
12/16/2009 1:04:09 PMConditionCounterMinAvgMaxHourly Trend
More than 30% CPU in Privileged Mode CPU - This may indicate a high I/O issue\\DB04\Processor(1)\% Privileged Time1924290
More than 30% CPU in Privileged Mode CPU - This may indicate a high I/O issue\\DB04\Processor(0)\% Privileged Time1825290
Not enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes7767767760
This process is using more than 1000 data I/O's per second\\DB04\Process(wmiprvse)\IO Data Operations/sec1121,0441,8980
This process is using more than 1000 data I/O's per second\\DB04\Process(lsass)\IO Data Operations/sec1491,0951,9780
This process is using more than 1000 other I/O's per second\\DB04\Process(lsass)\IO Other Operations/sec1741,2622,2790
Very low on available memory - less than 5% available\\DB04\Memory\Available MBytes4173860
High User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
More then 10 page file reads per second\\DB04\Memory\Pages Input/sec1161912440
> 10% of the number of Batch Requests/Sec\\DB04\SQLServer:Access Methods\FreeSpace Scans/sec02477420
Page Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy1826340
Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec39512,66132,6970
Latch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec0.3979.63526.2020
A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec0120
12/16/2009 1:04:28 PMConditionCounterMinAvgMaxHourly Trend
More than 30% CPU in Privileged Mode CPU - This may indicate a high I/O issue\\DB04\Processor(1)\% Privileged Time19253752
More than 30% CPU in Privileged Mode CPU - This may indicate a high I/O issue\\DB04\Processor(0)\% Privileged Time2533491,553
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0070.0270.0844.218
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0070.0310.14.982
Average disk responsiveness is slow - more than 15ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Write00.0130.0462.447
Average disk responsiveness is slow - more than 15ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Write00.0130.0462.446
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0070.0270.0844.219
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read00.3021.20155.937
Disk responsiveness is very slow (spike of more than 25ms)\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Write00.0130.0462.447
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Write00.2240.89142.495
Not enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes7767767760
Very low on available memory - less than 5% available\\DB04\Memory\Available MBytes811001185,211
High User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
More then 10 page file reads per second\\DB04\Memory\Pages Input/sec35149259-7,949
Ratio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec123221
More than 20 Workfiles created per second for every 100 Batch Requests \\DB04\SQLServer:Access Methods\Workfiles Created/sec513322,346
Page Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy3947553,932
Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec16,54634,53850,1244,145,035
Page Writes/sec > 90\\DB04\SQLServer:Buffer Manager\Page writes/sec013754725,893
Possible disparity between User Connections and Batch Requests per second\\DB04\SQLServer:General Statistics\User Connections11121247.3684210526316
Latch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec25.53860.73110.799,681.208
A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec245505
A ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations\\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec00169
12/16/2009 1:04:47 PMConditionCounterMinAvgMaxHourly Trend
More than 30% CPU in Privileged Mode CPU - This may indicate a high I/O issue\\DB04\Processor(1)\% Privileged Time1139561,394
More than 30% CPU in Privileged Mode CPU - This may indicate a high I/O issue\\DB04\Processor(0)\% Privileged Time172022-481
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read00.0720.216.419
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read00.0930.2728.392
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read00.0720.216.419
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(C:)\Avg. Disk sec/Read00.1030.3029.331
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(T:)\Avg. Disk sec/Write00.060.1775.636
Not enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes7767767760
Low on available memory - less than 10% available\\DB04\Memory\Available MBytes1171191214,389
High User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
More then 10 page file reads per second\\DB04\Memory\Pages Input/sec0926-17,168
> 10% of the number of Batch Requests/Sec\\DB04\SQLServer:Access Methods\FreeSpace Scans/sec041115-19,511
Ratio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec248314
Page Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy6065703,671
Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec23,63137,23144,6662,327,696
Possible disparity between User Connections and Batch Requests per second\\DB04\SQLServer:General Statistics\User Connections111111-47.3684210526316
Latch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec2.7841.72177.9233,039.707
A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec2613477
12/16/2009 1:05:06 PMConditionCounterMinAvgMaxHourly Trend
Not enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes7767767760
Low on available memory - less than 10% available\\DB04\Memory\Available MBytes1311311313,663
High User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
Increasing trend of more than 10MB's per hour detected\\DB04\Memory\System Cache Resident Bytes26,796,03226,846,20826,943,48821,212,968.4210526
More then 10 page file reads per second\\DB04\Memory\Pages Input/sec033132-9,930
Ratio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec011-22
Page Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy7582903,553
Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec0197494-787,200
A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec001-38
12/16/2009 1:05:25 PMConditionCounterMinAvgMaxHourly Trend
Not enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes7767767760
Low on available memory - less than 10% available\\DB04\Memory\Available MBytes1311311312,747
High User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
Increasing trend of more than 10MB's per hour detected\\DB04\Memory\System Cache Resident Bytes26,357,76026,733,56826,865,66410,574,147.3684211
Ratio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec011-19
Page Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy951021103,612
Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec0149294-592,692
A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec001-26
12/16/2009 1:05:44 PMConditionCounterMinAvgMaxHourly Trend
Not enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes7767767760
Low on available memory - less than 10% available\\DB04\Memory\Available MBytes1311311312,198
High User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
Ratio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec011-15
Page Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy1151231303,657
Possible disparity between User Connections and Batch Requests per second\\DB04\SQLServer:General Statistics\User Connections111111-18.9473684210526
A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec01517
12/16/2009 1:06:03 PMConditionCounterMinAvgMaxHourly Trend
Not enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes7767767760
Low on available memory - less than 10% available\\DB04\Memory\Available MBytes1311311311,832
High User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
Ratio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec011-11
Page Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy1351431513,687
Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec0166347-394,597
Latch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec00.4991.198-288.514
A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec001-19
12/16/2009 1:06:22 PMConditionCounterMinAvgMaxHourly Trend
Not enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes7767767760
Low on available memory - less than 10% available\\DB04\Memory\Available MBytes1311311311,570
High User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
Ratio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec001-18
Page Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy1561611663,647
Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2105281-339,882
A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec001-18
12/16/2009 1:06:41 PMConditionCounterMinAvgMaxHourly Trend
High processor utilization - more than 75% CPU utilization\\DB04\Processor(_Total)\% Processor Time2180100559
High processor utilization - more than 75% CPU utilization\\DB04\Processor(1)\% Processor Time2681100552
High processor utilization - more than 75% CPU utilization\\DB04\Processor(0)\% Processor Time1679100567
Excessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time191391833,014
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read00.0260.0570.514
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read00.0260.0590.525
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read00.0260.0570.514
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read00.030.0710.528
Not enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes7767767760
Low on available memory - less than 10% available\\DB04\Memory\Available MBytes1281291311,320
Memory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,450,659,8401,481,544,7041,493,245,95256,387,368.4210526
High User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
Ratio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec41521319
Page Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy1711781863,594
Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec8,96691,029139,0191,856,080
Page Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec01272572,506
Latch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec7.181206.715348.0544,667.668
A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec81118237
12/16/2009 1:07:00 PMConditionCounterMinAvgMaxHourly Trend
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time9999100909
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time9899100871
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time99100100947
Excessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1731781813,494
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read00.150.5293.07
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read00.150.5293.074
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read00.150.5293.07
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read00.1510.5293.032
Not enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes7767767760
Less than 80 I/O's per second on average when disk latency is longer than 25ms. This may indicate too many virtual LUNs using the same physical disks on a SAN. This was a spike - not an average.\\DB04\LogicalDisk(_Total)\Disk Transfers/sec91722-2,641
Less than 80 I/O's per second on average when disk latency is longer than 25ms. This may indicate too many virtual LUNs using the same physical disks on a SAN. This was a spike - not an average.\\DB04\LogicalDisk(S:)\Disk Transfers/sec059-34
Low on available memory - less than 10% available\\DB04\Memory\Available MBytes1171231281,047
Memory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,492,819,9681,499,601,9201,508,446,208430,274,021.052632
High User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
Ratio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec121519293
Free Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages366301,229-197,626
Page Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy1911982063,621
Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec80,318101,723115,1691,874,984
Page Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec22474914,754
Latch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec175.544227.277288.6784,581.939
A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec4814138
12/16/2009 1:07:19 PMConditionCounterMinAvgMaxHourly Trend
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time99100100821
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time99100100788
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time99100100854
Excessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1781801833,197
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0320.050.0610.875
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0330.0520.0630.903
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0320.050.0610.875
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0350.0520.0630.853
Not enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes7767767760
Low on available memory - less than 10% available\\DB04\Memory\Available MBytes117117117834
Memory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,508,077,5681,508,388,8641,508,675,584553,736,084.210526
High User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
Increasing trend of more than 10MB's per hour detected\\DB04\Memory\System Cache Resident Bytes27,045,88827,096,06427,156,48011,098,004.2105263
Ratio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec121518271
Free Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages165286417-184,372
Page Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy2102172213,614
Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec88,46099,527107,9601,645,870
Page Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec2462472484,283
Latch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec175.184229.149307.8884,159.201
A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec51015175
12/16/2009 1:07:38 PMConditionCounterMinAvgMaxHourly Trend
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time100100100747
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time99100100716
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time99100100778
Excessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1781841922,962
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0140.0360.0610.545
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0180.0380.0610.573
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0140.0360.0610.545
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0180.0380.0610.522
Not enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes7767767760
Low on available memory - less than 10% available\\DB04\Memory\Available MBytes117117117758
Memory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,508,528,1281,512,427,5201,514,430,464572,961,806.698565
High User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
Increasing trend of more than 10MB's per hour detected\\DB04\Memory\System Cache Resident Bytes27,172,86427,215,18927,254,78412,141,014.354067
Ratio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec7913142
Free Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages139186250-169,332
Page Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy2212212213,355
Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec8,16555,304105,712734,517
Page Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec1242884954,612
Latch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec13.127152.942238.862,468.446
A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec371197
12/16/2009 1:07:57 PMConditionCounterMinAvgMaxHourly Trend
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time99100100685
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time98100100655
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time99100100714
Excessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1871911952,835
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0290.030.0310.401
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0310.0310.0320.428
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0290.030.0310.401
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0310.0320.0320.383
Not enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes7767767760
Low on available memory - less than 10% available\\DB04\Memory\Available MBytes116116117683
Memory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,514,323,9681,514,323,9681,514,323,968555,158,905.263158
High User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
Increasing trend of more than 10MB's per hour detected\\DB04\Memory\System Cache Resident Bytes27,271,16827,334,65627,394,04813,015,578.9473684
Ratio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec04848
Free Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages104121127-156,257
Page Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy2212212213,075
Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2,0692,6183,159-158,583
Page Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec4946187439,435
Latch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec0.3961.7413.19-124.642
A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec051061
12/16/2009 1:08:16 PMConditionCounterMinAvgMaxHourly Trend
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time100100100634
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time99100100608
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time100100100660
Excessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1891901932,606
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.020.0290.0340.356
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0210.030.0360.38
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.020.0290.0340.356
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0210.030.0360.337
Not enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes7767767760
Very low on available memory - less than 5% available\\DB04\Memory\Available MBytes97111116557
Memory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,514,323,9681,519,169,5361,533,706,240583,078,037.246964
High User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
Increasing trend of more than 10MB's per hour detected\\DB04\Memory\System Cache Resident Bytes27,426,81627,453,44027,475,96813,745,645.3441296
Ratio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec02621
Free Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages111157251-143,705
Page Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy591802212,248
Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2,1502,4272,809-149,170
Page Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec6036136188,638
Latch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec00.9432.385-126.682
A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec03627
A ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations\\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec0012
12/16/2009 1:08:35 PMConditionCounterMinAvgMaxHourly Trend
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time100100100589
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time100100100566
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time99100100612
Excessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1821891922,394
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0280.0290.0310.341
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.030.0310.0330.359
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0280.0290.0310.341
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.030.0310.0330.32
Not enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes7767767760
Very low on available memory - less than 5% available\\DB04\Memory\Available MBytes939494281
Memory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,538,629,6321,538,629,6321,538,629,632804,799,326.31579
High User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
Ratio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec14843
Free Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages25154241-133,488
Page Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy595959443
Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2,1282,5873,082-136,340
Page Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec6166176188,066
Latch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec0.5941.7853.369-106.25
A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec05954
A ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations\\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec0013
12/16/2009 1:08:54 PMConditionCounterMinAvgMaxHourly Trend
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time100100100550
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time100100100529
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time100100100570
Excessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1881911942,266
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0280.0320.0370.347
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0290.0330.0380.369
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0280.0320.0370.347
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0290.0340.0390.333
Not enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes704758776-227
Very low on available memory - less than 5% available\\DB04\Memory\Available MBytes949494265
Memory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,538,629,6321,538,629,6321,538,629,632751,146,037.894737
High User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
Ratio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec04839
Free Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages180204237-123,954
Page Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy595959414
Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2,2162,6733,177-126,162
Page Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec5215876207,153
Latch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec0.5971.7363.173-99.785
A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec051049
12/16/2009 1:09:13 PMConditionCounterMinAvgMaxHourly Trend
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time100100100517
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time100100100497
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time100100100537
Excessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1851921962,135
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.030.0310.0320.315
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0310.0320.0330.334
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.030.0310.0320.315
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0310.0330.0330.299
Disk responsiveness is very slow (spike of more than 25ms)\\DB04\LogicalDisk(C:)\Avg. Disk sec/Read00.010.0310.071
Not enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes704704704-853
Very low on available memory - less than 5% available\\DB04\Memory\Available MBytes949494249
Memory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,538,629,6321,538,629,6321,538,629,632704,199,410.526316
High User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
Ratio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec03921
Free Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages140209306-116,143
Page Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy444444210
Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2,1172,3702,707-121,876
Page Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec4966197437,088
Latch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec0.5961.2612.59-99.167
A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec031028
12/16/2009 1:09:32 PMConditionCounterMinAvgMaxHourly Trend
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time9999100481
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time9999100462
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time9999100500
Excessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1871901921,982
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0320.0350.0440.346
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0340.0370.0470.369
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0320.0350.0440.347
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0340.0370.0470.336
Not enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes704704704-802
Very low on available memory - less than 5% available\\DB04\Memory\Available MBytes939494231
Memory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,538,629,6321,538,629,6321,538,629,632662,775,915.789474
High User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
Ratio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec04835
Free Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages147185238-109,580
Page Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy444444198
Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2,3672,6572,974-111,499
Page Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec4935557395,955
Latch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec1.1881.6862.575-88.597
A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec051043
12/16/2009 1:09:51 PMConditionCounterMinAvgMaxHourly Trend
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time100100100457
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time99100100439
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time100100100475
Excessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1861901971,873
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0320.0350.040.325
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0330.0370.0420.346
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0320.0350.040.325
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0330.0370.0420.315
Not enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes704704704-758
Very low on available memory - less than 5% available\\DB04\Memory\Available MBytes939393211
Memory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,538,629,6321,538,629,6321,538,629,632625,955,031.578947
High User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
Ratio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec13723
Free Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages123208385-103,253
Page Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy444650208
Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2,3522,5592,953-106,338
Page Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec4946187406,290
Latch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec0.7971.4892.382-85.748
A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec14927
A ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations\\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec0012
12/16/2009 1:10:10 PMConditionCounterMinAvgMaxHourly Trend
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time99100100432
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time99100100416
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time99100100449
Excessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1861891911,773
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0340.0380.0490.341
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0360.0410.0520.364
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0340.0380.0490.341
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0360.0410.0520.334
Not enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes704704704-718
Very low on available memory - less than 5% available\\DB04\Memory\Available MBytes939393199
Memory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,538,629,6321,538,629,6321,538,629,632593,010,029.916898
High User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
Ratio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec03924
Free Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages128177248-98,125
Lazy Writes/second > 20\\DB04\SQLServer:Buffer Manager\Lazy writes/sec324356426
Page Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy566471371
Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2,1242,5903,059-100,439
Page Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec4965896205,666
Latch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec0.1991.1942.188-84.178
A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec041033
12/16/2009 1:10:29 PMConditionCounterMinAvgMaxHourly Trend
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time100100100412
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time100100100398
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time99100100427
Excessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1851911941,695
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0290.0340.040.283
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0310.0360.0430.303
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0290.0340.040.283
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0310.0360.0430.275
Not enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes704704704-682
Very low on available memory - less than 5% available\\DB04\Memory\Available MBytes939393189
Memory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,538,695,1681,538,695,1681,538,695,168563,980,395.789474
High User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
Ratio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec06842
Free Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages90180268-93,196
Lazy Writes/second > 20\\DB04\SQLServer:Buffer Manager\Lazy writes/sec02265205
Page Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy767980497
Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec1,7122,5693,373-95,613
Page Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec4965797435,288
Latch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec0.3981.3932.785-78.085
A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec071052
12/16/2009 1:10:48 PMConditionCounterMinAvgMaxHourly Trend
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time100100100393
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time100100100377
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time99100100408
Excessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1861901921,605
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.030.0330.0360.256
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0310.0350.0380.274
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.030.0330.0360.256
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0310.0360.0390.256
Not enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes704704704-650
Very low on available memory - less than 5% available\\DB04\Memory\Available MBytes929395180
Memory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,538,695,1681,538,695,1681,538,695,168537,124,186.466165
High User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
Ratio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec02812
Free Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages144188231-88,687
Page Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy808080485
Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2,3532,6202,917-90,600
Page Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec4946187435,386
Latch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec0.9921.7362.583-71.27
A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec03916
A ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations\\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec0011
12/16/2009 1:11:07 PMConditionCounterMinAvgMaxHourly Trend
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time100100100375
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time99100100360
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time100100100390
Excessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1851891931,528
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0340.0380.0420.288
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0360.040.0440.305
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0340.0380.0420.288
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0360.040.0440.28
Not enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes704704704-620
Very low on available memory - less than 5% available\\DB04\Memory\Available MBytes949495185
Memory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,538,695,1681,538,695,1681,538,695,168512,709,450.717703
High User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
Ratio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec14727
Free Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages160215372-84,421
Page Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy808080463
Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2,5252,7303,024-85,533
Page Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec4955887424,888
Latch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec1.1951.9892.583-65.853
A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec15934
A ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations\\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec0012
12/16/2009 1:11:26 PMConditionCounterMinAvgMaxHourly Trend
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time9097100339
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time8997100323
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time9198100355
Excessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1721851931,424
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0290.080.230.626
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.030.0850.2460.668
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0290.080.230.626
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.030.0850.2460.644
Not enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes704704704-593
Very low on available memory - less than 5% available\\DB04\Memory\Available MBytes949494173
Memory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,538,695,1681,538,695,1681,538,695,168490,417,735.469108
High User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
Ratio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec04926
Free Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages115169255-81,130
Page Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy647680410
Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2,1262,4893,168-83,802
Page Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec4935566194,411
Latch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec0.5961.2392.572-69.169
A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec051133
12/16/2009 1:11:45 PMConditionCounterMinAvgMaxHourly Trend
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time99100100343
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time99100100329
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time99100100356
Excessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1821881921,394
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0320.0370.0430.255
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0340.0390.0460.272
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0320.0370.0430.255
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0340.0390.0460.249
Not enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes704704704-568
Very low on available memory - less than 5% available\\DB04\Memory\Available MBytes949494166
Memory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,538,695,1681,538,695,1681,538,695,168469,983,663.157895
High User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
Ratio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec02611
Free Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages72134203-78,022
Page Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy646464298
Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2,2942,5182,983-80,080
Page Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec4945887434,481
Latch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec0.5951.893.381-61.148
A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec03914
A ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations\\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec0011
12/16/2009 1:12:04 PMConditionCounterMinAvgMaxHourly Trend
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time100100100329
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time100100100317
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time99100100341
Excessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1841881921,340
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0370.0370.0380.251
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0390.040.0410.268
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0370.0370.0380.251
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0390.040.0410.246
Not enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes704704704-546
Very low on available memory - less than 5% available\\DB04\Memory\Available MBytes949494159
Memory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,538,695,1681,538,695,1681,538,695,168451,184,316.631579
High User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
Ratio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec15832
Free Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages163208255-74,339
Page Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy646464286
Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2,4082,7332,960-75,243
Page Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec4965787434,227
Latch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec0.9941.6582.587-60.456
A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec16941
A ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations\\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec0012
12/16/2009 1:12:23 PMConditionCounterMinAvgMaxHourly Trend
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time100100100318
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time100100100306
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time100100100329
Excessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1831881921,288
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0280.0320.0350.199
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0290.0330.0360.21
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0280.0320.0350.199
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0290.0330.0360.189
Not enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes704704704-525
Very low on available memory - less than 5% available\\DB04\Memory\Available MBytes949494153
Memory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,538,695,1681,538,695,1681,538,695,168433,831,073.684211
High User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
Ratio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec02810
Free Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages128166184-71,790
Page Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy646464275
Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2,1392,5603,214-73,613
Page Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec4945846204,104
Latch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec0.5961.6382.388-58.279
A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec031013
12/16/2009 1:12:42 PMConditionCounterMinAvgMaxHourly Trend
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time99100100303
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time99100100291
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time99100100316
Excessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1851881901,241
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.030.0350.0460.217
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0320.0370.0480.231
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.030.0350.0460.217
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0330.0370.0480.212
Not enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes704704704-505
Very low on available memory - less than 5% available\\DB04\Memory\Available MBytes949596154
Memory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,538,695,1681,538,695,1681,538,695,168417,763,256.140351
High User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
Ratio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec04922
Free Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages101227379-68,704
Page Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy626264254
Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec1,7322,6313,402-70,385
Page Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec3725577443,766
Latch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec0.5971.8393.585-54.709
A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec051128
12/16/2009 1:13:01 PMConditionCounterMinAvgMaxHourly Trend
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time100100100295
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time100100100284
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time100100100306
Excessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1851891941,202
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.030.0360.0430.211
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0310.0380.0460.225
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.030.0360.0430.211
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0320.0380.0460.207
Not enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes704704704-487
Very low on available memory - less than 5% available\\DB04\Memory\Available MBytes979797162
Memory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,538,695,1681,538,727,9361,538,826,240403,064,878.195489
High User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
Ratio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec14822
Free Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages92178231-66,581
Page Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy626262242
Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2,3512,7373,060-67,158
Page Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec4956197444,051
Latch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec0.3981.8882.982-52.423
A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec15927
A ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations\\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec0012
12/16/2009 1:13:20 PMConditionCounterMinAvgMaxHourly Trend
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time99100100284
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time99100100272
Very high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time100100100296
Excessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1891941981,194
Disk responsiveness is very slow (spike of more than 25ms)\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0020.0120.030.047
Disk responsiveness is very slow (spike of more than 25ms)\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read00.0110.0320.042
Disk responsiveness is very slow (spike of more than 25ms)\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0020.0120.030.047
Disk responsiveness is very slow (spike of more than 25ms)\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read00.0110.0320.023
Not enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes704704704-470
Very low on available memory - less than 5% available\\DB04\Memory\Available MBytes9799103170
Memory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,532,592,1281,536,638,9761,538,695,168375,517,711.796733
High User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
Ratio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec13713
Free Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages66198400-64,155
Page Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy626262234
Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2,4572,7152,888-64,984
Page Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec0121364657
Latch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec0.3980.7971.595-57.743
A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec14918
A ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations\\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec0011
12/16/2009 1:13:39 PMConditionCounterMinAvgMaxHourly Trend
Excessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time67117167666
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0090.0710.1330.419
Average disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0090.0710.1330.422
Average disk responsiveness is slow - more than 15ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Write0.0020.0120.0230.076
Average disk responsiveness is slow - more than 15ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Write0.0020.0120.0230.076
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0090.0710.1330.419
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0090.0710.1330.403
Disk responsiveness is very slow (spike of more than 25ms)\\DB04\LogicalDisk(T:)\Avg. Disk sec/Write0.0030.0150.0270.091
Average disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Write00.0270.0550.171
Not enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes704704704-455
Low on available memory - less than 10% available\\DB04\Memory\Available MBytes115115115265
Memory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,520,164,8641,522,061,3121,523,957,760270,930,997.894737
High User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
Ratio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec12172299
Free Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages148182217-62,113
Page Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy515151156
Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec75,77890,860105,942493,887
Page Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec13,7557,50923,584
Latch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec234.0031,122.0252,010.0487,025.623
A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec6111666
Back to the top

Processor


Processor Utilization Analysis

Description: % Processor Time is the percentage of elapsed time that the processor spends to execute a non-Idle thread. It is calculated by measuring the duration of the idle thread is active in the sample interval, and subtracting that time from interval duration. (Each processor has an idle thread that consumes cycles when no other threads are ready to run). This counter is the primary indicator of processor activity, and displays the average percentage of busy time observed during the sample interval. It is calculated by monitoring the time that the service is inactive, and subtracting that value from 100%. This analysis checks for utilization greater than 60% on each individual processor. If so, determine if it is high user mode CPU or high privileged mode. If high privileged mode CPU is suspected, then see the Privileged Mode CPU Analysis. If a user-mode processor bottleneck is suspected, then consider using a process profiler to analyze the functions causing the high CPU consumption. See “How To: Identify Functions causing a High User-mode CPU Bottleneck for Server Applications in a Production Environment” article in the references section for more information.

If a user-mode processor bottleneck is suspected, then consider using a process profiler to analyze the functions causing the high CPU consumption. See “How To: Identify Functions causing a High User-mode CPU Bottleneck for Server Applications in a Production Environment” article in the references section for more information.

References:
Measuring .NET Application Performance
http://msdn2.microsoft.com/en-us/library/ms998579.aspx

How To: Identify Functions causing a High User-mode CPU Bottleneck for Server Applications in a Production Environment http://www.codeplex.com/PerfTesting/Wiki/View.aspx?title=How%20To%3a%20Identify%20a%20Disk%20Performance%20Bottleneck%20Using%20SPA&referringTitle=How%20Tos

\Processor(*)\% Processor Time

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\Processor(_Total)\% Processor Time9801005032879498
\\DB04\Processor(1)\% Processor Time14821005530889498
\\DB04\Processor(0)\% Processor Time3791004634869398
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
12/16/2009 1:06:41 PMHigh processor utilization - more than 75% CPU utilization\\DB04\Processor(_Total)\% Processor Time2180100559
12/16/2009 1:07:00 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time9999100909
12/16/2009 1:07:19 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time99100100821
12/16/2009 1:07:38 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time100100100747
12/16/2009 1:07:57 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time99100100685
12/16/2009 1:08:16 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time100100100634
12/16/2009 1:08:35 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time100100100589
12/16/2009 1:08:54 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time100100100550
12/16/2009 1:09:13 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time100100100517
12/16/2009 1:09:32 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time9999100481
12/16/2009 1:09:51 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time100100100457
12/16/2009 1:10:10 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time99100100432
12/16/2009 1:10:29 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time100100100412
12/16/2009 1:10:48 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time100100100393
12/16/2009 1:11:07 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time100100100375
12/16/2009 1:11:26 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time9097100339
12/16/2009 1:11:45 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time99100100343
12/16/2009 1:12:04 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time100100100329
12/16/2009 1:12:23 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time100100100318
12/16/2009 1:12:42 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time99100100303
12/16/2009 1:13:01 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time100100100295
12/16/2009 1:13:20 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(_Total)\% Processor Time99100100284
12/16/2009 1:06:41 PMHigh processor utilization - more than 75% CPU utilization\\DB04\Processor(1)\% Processor Time2681100552
12/16/2009 1:07:00 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time9899100871
12/16/2009 1:07:19 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time99100100788
12/16/2009 1:07:38 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time99100100716
12/16/2009 1:07:57 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time98100100655
12/16/2009 1:08:16 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time99100100608
12/16/2009 1:08:35 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time100100100566
12/16/2009 1:08:54 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time100100100529
12/16/2009 1:09:13 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time100100100497
12/16/2009 1:09:32 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time9999100462
12/16/2009 1:09:51 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time99100100439
12/16/2009 1:10:10 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time99100100416
12/16/2009 1:10:29 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time100100100398
12/16/2009 1:10:48 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time100100100377
12/16/2009 1:11:07 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time99100100360
12/16/2009 1:11:26 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time8997100323
12/16/2009 1:11:45 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time99100100329
12/16/2009 1:12:04 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time100100100317
12/16/2009 1:12:23 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time100100100306
12/16/2009 1:12:42 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time99100100291
12/16/2009 1:13:01 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time100100100284
12/16/2009 1:13:20 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(1)\% Processor Time99100100272
12/16/2009 1:06:41 PMHigh processor utilization - more than 75% CPU utilization\\DB04\Processor(0)\% Processor Time1679100567
12/16/2009 1:07:00 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time99100100947
12/16/2009 1:07:19 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time99100100854
12/16/2009 1:07:38 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time99100100778
12/16/2009 1:07:57 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time99100100714
12/16/2009 1:08:16 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time100100100660
12/16/2009 1:08:35 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time99100100612
12/16/2009 1:08:54 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time100100100570
12/16/2009 1:09:13 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time100100100537
12/16/2009 1:09:32 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time9999100500
12/16/2009 1:09:51 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time100100100475
12/16/2009 1:10:10 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time99100100449
12/16/2009 1:10:29 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time99100100427
12/16/2009 1:10:48 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time99100100408
12/16/2009 1:11:07 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time100100100390
12/16/2009 1:11:26 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time9198100355
12/16/2009 1:11:45 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time99100100356
12/16/2009 1:12:04 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time99100100341
12/16/2009 1:12:23 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time100100100329
12/16/2009 1:12:42 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time99100100316
12/16/2009 1:13:01 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time100100100306
12/16/2009 1:13:20 PMVery high processor utilization - more than 90% CPU utilization\\DB04\Processor(0)\% Processor Time100100100296
Back to the top

Privileged Mode CPU Analysis

Description: This counter indicates the percentage of time a thread runs in privileged mode. When your application calls operating system functions (for example to perform file or network I/O or to allocate memory), these operating system functions are executed in privileged mode.

High privileged mode CPU indicates that computer is spending too much time in system I/O versus real (user mode) work. % Privileged Time is the percentage of elapsed time that the process threads spent executing code in privileged mode. When a Windows system service in called, the service will often run in privileged mode to gain access to system-private data. Such data is protected from access by threads executing in user mode. Calls to the system can be explicit or implicit, such as page faults or interrupts. Unlike some early operating systems, Windows uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes. Some work done by Windows on behalf of the application might appear in other subsystem processes in addition to the privileged time in the process.

This analysis checks to see if privileged mode CPU is consuming more than 30% of total CPU. If so, then the CPU consumption is likely caused by another bottleneck other than the processor such as network, memory, or disk I/O.

References:
Measuring .NET Application Performance
http://msdn2.microsoft.com/en-us/library/ms998579.aspx

\Processor(*)\% Privileged Time

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\Processor(_Total)\% Privileged Time0438-1418322
\\DB04\Processor(1)\% Privileged Time0456-1479211
\\DB04\Processor(0)\% Privileged Time0549-1357333
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
12/16/2009 1:04:09 PMMore than 30% CPU in Privileged Mode CPU - This may indicate a high I/O issue\\DB04\Processor(1)\% Privileged Time1924290
12/16/2009 1:04:28 PMMore than 30% CPU in Privileged Mode CPU - This may indicate a high I/O issue\\DB04\Processor(1)\% Privileged Time19253752
12/16/2009 1:04:47 PMMore than 30% CPU in Privileged Mode CPU - This may indicate a high I/O issue\\DB04\Processor(1)\% Privileged Time1139561,394
12/16/2009 1:04:09 PMMore than 30% CPU in Privileged Mode CPU - This may indicate a high I/O issue\\DB04\Processor(0)\% Privileged Time1825290
12/16/2009 1:04:28 PMMore than 30% CPU in Privileged Mode CPU - This may indicate a high I/O issue\\DB04\Processor(0)\% Privileged Time2533491,553
12/16/2009 1:04:47 PMMore than 30% CPU in Privileged Mode CPU - This may indicate a high I/O issue\\DB04\Processor(0)\% Privileged Time172022-481
Back to the top

Excessive Processor Use by Processes

Description: This analysis checks all of the processes to determine if any of the processes are consuming a large amount of CPU.

If a user-mode processor bottleneck is suspected, then consider using a process profiler to analyze the functions causing the high CPU consumption. See “How To: Identify Functions causing a High User-mode CPU Bottleneck for Server Applications in a Production Environment” article in the references section for more information.

References:
Measuring .NET Application Performance
http://msdn2.microsoft.com/en-us/library/ms998579.aspx

How To: Identify Functions causing a High User-mode CPU Bottleneck for Server Applications in a Production Environment http://www.codeplex.com/PerfTesting/Wiki/View.aspx?title=How%20To%3a%20Identify%20a%20Disk%20Performance%20Bottleneck%20Using%20SPA&referringTitle=How%20Tos

\Process(*)\% Processor Time

\Process(*)\% Processor Time

\Process(*)\% Processor Time

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\Process(_Total)\% Processor Time1271901991446191191192
\\DB04\Process(dfrgifc)\% Processor Time001-0---
\\DB04\Process(powershell#4)\% Processor Time--------
\\DB04\Process(cmd#4)\% Processor Time--------
\\DB04\Process(powershell#3)\% Processor Time--------
\\DB04\Process(cmd#3)\% Processor Time--------
\\DB04\Process(powershell#2)\% Processor Time0210-21222
\\DB04\Process(cmd#2)\% Processor Time0-000---
\\DB04\Process(SQLCMD#1)\% Processor Time--------
\\DB04\Process(SQLCMD)\% Processor Time001-10000
\\DB04\Process(msinfo32)\% Processor Time028-2531---
\\DB04\Process(cmd#1)\% Processor Time0-000---
\\DB04\Process(SQLdiag)\% Processor Time001-20000
\\DB04\Process(powershell#1)\% Processor Time0-000---
\\DB04\Process(cmd)\% Processor Time0-000---
\\DB04\Process(explorer#1)\% Processor Time001-100--
\\DB04\Process(svchost#8)\% Processor Time0-000---
\\DB04\Process(SQLAGENT)\% Processor Time00100000
\\DB04\Process(fdhost)\% Processor Time00000---
\\DB04\Process(sqlservr)\% Processor Time013919866676151167183
\\DB04\Process(Ssms)\% Processor Time012-30100
\\DB04\Process(wpabaln)\% Processor Time0-000---
\\DB04\Process(powershell)\% Processor Time0-000---
\\DB04\Process(wmiprvse#1)\% Processor Time00000---
\\DB04\Process(explorer)\% Processor Time0-000---
\\DB04\Process(wmiprvse)\% Processor Time0681-33916300
\\DB04\Process(alg)\% Processor Time0-000---
\\DB04\Process(fdlauncher)\% Processor Time0-000---
\\DB04\Process(svchost#7)\% Processor Time00000---
\\DB04\Process(sqlwriter)\% Processor Time0-000---
\\DB04\Process(svchost#6)\% Processor Time00000---
\\DB04\Process(MsDtsSrvr)\% Processor Time0-000---
\\DB04\Process(svchost#5)\% Processor Time0-000---
\\DB04\Process(msdtc)\% Processor Time0-000---
\\DB04\Process(vmicsvc#4)\% Processor Time0-000---
\\DB04\Process(vmicsvc#3)\% Processor Time0000000-
\\DB04\Process(vmicsvc#2)\% Processor Time0-000---
\\DB04\Process(vmicsvc#1)\% Processor Time0-000---
\\DB04\Process(vmicsvc)\% Processor Time000-10000
\\DB04\Process(spoolsv)\% Processor Time00000---
\\DB04\Process(svchost#4)\% Processor Time0115-682000
\\DB04\Process(svchost#3)\% Processor Time0001000-
\\DB04\Process(svchost#2)\% Processor Time0-000---
\\DB04\Process(svchost#1)\% Processor Time002-5000-
\\DB04\Process(svchost)\% Processor Time000-10---
\\DB04\Process(lsass)\% Processor Time0114-542000
\\DB04\Process(services)\% Processor Time0116-112111
\\DB04\Process(winlogon)\% Processor Time0-000---
\\DB04\Process(csrss)\% Processor Time003-11000
\\DB04\Process(smss)\% Processor Time0-000---
\\DB04\Process(System)\% Processor Time003-130000
\\DB04\Process(Idle)\% Processor Time039181-1016533178
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
*OK\\DB04\Process(dfrgifc)\% Processor Time001-
*OK\\DB04\Process(powershell#4)\% Processor Time----
*OK\\DB04\Process(cmd#4)\% Processor Time----
*OK\\DB04\Process(powershell#3)\% Processor Time----
*OK\\DB04\Process(cmd#3)\% Processor Time----
*OK\\DB04\Process(powershell#2)\% Processor Time0210-2
*OK\\DB04\Process(cmd#2)\% Processor Time0-00
*OK\\DB04\Process(SQLCMD#1)\% Processor Time----
*OK\\DB04\Process(SQLCMD)\% Processor Time001-1
*OK\\DB04\Process(msinfo32)\% Processor Time028-253
*OK\\DB04\Process(cmd#1)\% Processor Time0-00
*OK\\DB04\Process(SQLdiag)\% Processor Time001-2
*OK\\DB04\Process(powershell#1)\% Processor Time0-00
*OK\\DB04\Process(cmd)\% Processor Time0-00
*OK\\DB04\Process(explorer#1)\% Processor Time001-1
*OK\\DB04\Process(svchost#8)\% Processor Time0-00
*OK\\DB04\Process(SQLAGENT)\% Processor Time0010
*OK\\DB04\Process(fdhost)\% Processor Time0000
12/16/2009 1:06:41 PMExcessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time191391833,014
12/16/2009 1:07:00 PMExcessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1731781813,494
12/16/2009 1:07:19 PMExcessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1781801833,197
12/16/2009 1:07:38 PMExcessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1781841922,962
12/16/2009 1:07:57 PMExcessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1871911952,835
12/16/2009 1:08:16 PMExcessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1891901932,606
12/16/2009 1:08:35 PMExcessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1821891922,394
12/16/2009 1:08:54 PMExcessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1881911942,266
12/16/2009 1:09:13 PMExcessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1851921962,135
12/16/2009 1:09:32 PMExcessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1871901921,982
12/16/2009 1:09:51 PMExcessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1861901971,873
12/16/2009 1:10:10 PMExcessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1861891911,773
12/16/2009 1:10:29 PMExcessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1851911941,695
12/16/2009 1:10:48 PMExcessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1861901921,605
12/16/2009 1:11:07 PMExcessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1851891931,528
12/16/2009 1:11:26 PMExcessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1721851931,424
12/16/2009 1:11:45 PMExcessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1821881921,394
12/16/2009 1:12:04 PMExcessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1841881921,340
12/16/2009 1:12:23 PMExcessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1831881921,288
12/16/2009 1:12:42 PMExcessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1851881901,241
12/16/2009 1:13:01 PMExcessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1851891941,202
12/16/2009 1:13:20 PMExcessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time1891941981,194
12/16/2009 1:13:39 PMExcessive Processor Use Suspected - more than 80% CPU utilization\\DB04\Process(sqlservr)\% Processor Time67117167666
Back to the top

Interrupt Time

Description: % Interrupt Time is the time the processor spends receiving and servicing hardware interrupts during sample intervals. This value is an indirect indicator of the activity of devices that generate interrupts, such as the system clock, the mouse, disk drivers, data communication lines, network interface cards and other peripheral devices. These devices normally interrupt the processor when they have completed a task or require attention. Normal thread execution is suspended during interrupts. Most system clocks interrupt the processor every 10 milliseconds, creating a background of interrupt activity. A dramatic increase in this counter indicates potential hardware problems.

This analysis checks for % Interrupt Time greater than 30%. If this occurs, then consider updating devices drivers for hardware that correlates to this alert.

References:
Measuring .NET Application Performance
http://msdn2.microsoft.com/en-us/library/ms998579.aspx

\Processor(*)\% Interrupt Time

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\Processor(_Total)\% Interrupt Time000-10000
\\DB04\Processor(1)\% Interrupt Time000-1000-
\\DB04\Processor(0)\% Interrupt Time001-10000
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
*OK\\DB04\Processor(_Total)\% Interrupt Time000-1
*OK\\DB04\Processor(1)\% Interrupt Time000-1
*OK\\DB04\Processor(0)\% Interrupt Time001-1
Back to the top

Network


Network Utilization Analysis

Description: Bytes Total/sec is the rate at which bytes are sent and received over each network adapter, including framing characters. Network Interface\Bytes Received/sec is a sum of Network Interface\Bytes Received/sec and Network Interface\Bytes Sent/sec. This counter indicates the rate at which bytes are sent and received over each network adapter. This counter helps you know whether the traffic at your network adapter is saturated and if you need to add another network adapter. How quickly you can identify a problem depends on the type of network you have as well as whether you share bandwidth with other applications.

This analysis converts Bytes Total/sec to bits and compares it to the current bandwidth of the network adapter to calculate network utilization. Next, it checks for utilization above 50%.
Reference:
Measuring .NET Application Performance
http://msdn2.microsoft.com/en-us/library/ms998579.aspx


\Network Interface(*)\Bytes Total/sec

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\Network Interface(MS TCP Loopback interface)\Bytes Total/sec01165-1319111113
\\DB04\Network Interface(Microsoft Virtual Machine Bus Network Adapter)\Bytes Total/sec031,836745,86464,27747,43525,43226,81327,873
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
*OK\\DB04\Network Interface(MS TCP Loopback interface)\Bytes Total/sec01165-131
*OK\\DB04\Network Interface(Microsoft Virtual Machine Bus Network Adapter)\Bytes Total/sec031,836745,86464,277
Back to the top

Network Output Queue Length Analysis

Description: This analysis checks to see how many threads are waiting on the network adapter. If there are a lot of threads waiting on the network adapter, then the system is most likely saturating the network I/O most likely due to network latency or network bandwidth.

Output Queue Length is the length of the output packet queue (in packets). If this is longer than two, there are delays and the bottleneck should be found and eliminated, if possible. Since the requests are queued by the Network Driver Interface Specification (NDIS) in this implementation, this will always be 0.

\Network Interface(*)\Output Queue Length

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\Network Interface(MS TCP Loopback interface)\Output Queue Length0-000---
\\DB04\Network Interface(Microsoft Virtual Machine Bus Network Adapter)\Output Queue Length0-000---
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
*OK\\DB04\Network Interface(MS TCP Loopback interface)\Output Queue Length0-00
*OK\\DB04\Network Interface(Microsoft Virtual Machine Bus Network Adapter)\Output Queue Length0-00
Back to the top

Memory Committed Bytes

Description: Committed Bytes is the amount of committed virtual memory, in bytes. Committed memory is the physical memory which has space reserved on the disk paging file(s). There can be one or more paging files on each physical drive. This counter displays the last observed value only; it is not an average.

\Memory\Committed Bytes

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\Memory\Committed Bytes2,150,879,2322,219,603,9022,309,332,992-24,136,21935,119,3302,225,144,7532,231,806,4472,236,579,840
Back to the top

Disk


Physical Disk Interface Analysis

Description: This analysis analyzes the idle time of each of the physical disks. The more idle the disk, the less the disk is being used. This counter is best used to determine if there is a bottleneck in the disk interface such as SAN fabric or SCSI controller.

% Idle Time reports the percentage of time during the sample interval that the disk was idle.

Reference:
Ruling Out Disk-Bound Problems
http://technet.microsoft.com/en-us/library/5bcdd349-dcc6-43eb-9dc3-54175f7061ad.aspx


\PhysicalDisk(*)\% Idle Time

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\PhysicalDisk(_Total)\% Idle Time5996100-374979797
\\DB04\PhysicalDisk(1 P:)\% Idle Time9910010110100100100
\\DB04\PhysicalDisk(0 C: S: T:)\% Idle Time1892100-769949393
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
*OK\\DB04\PhysicalDisk(_Total)\% Idle Time5996100-37
*OK\\DB04\PhysicalDisk(1 P:)\% Idle Time991001011
*OK\\DB04\PhysicalDisk(0 C: S: T:)\% Idle Time1892100-76
Back to the top

Logical Disk Interface Analysis

Description: This analysis analyzes the idle time of each of the physical disks. The more idle the disk, the less the disk is being used. This counter is best used to determine if there is a bottleneck in the disk interface such as SAN fabric or SCSI controller.

% Idle Time reports the percentage of time during the sample interval that the disk was idle.

Reference:
Ruling Out Disk-Bound Problems
http://technet.microsoft.com/en-us/library/5bcdd349-dcc6-43eb-9dc3-54175f7061ad.aspx


\LogicalDisk(*)\% Idle Time

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\LogicalDisk(_Total)\% Idle Time7598100-303999999
\\DB04\LogicalDisk(P:)\% Idle Time9910010110100100100
\\DB04\LogicalDisk(T:)\% Idle Time86100101-321100100100
\\DB04\LogicalDisk(S:)\% Idle Time1994101-2407969595
\\DB04\LogicalDisk(C:)\% Idle Time50971001536999999
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
*OK\\DB04\LogicalDisk(_Total)\% Idle Time7598100-30
*OK\\DB04\LogicalDisk(P:)\% Idle Time991001011
*OK\\DB04\LogicalDisk(T:)\% Idle Time86100101-32
*OK\\DB04\LogicalDisk(S:)\% Idle Time1994101-240
*OK\\DB04\LogicalDisk(C:)\% Idle Time5097100153
Back to the top

Physical Disk Read Latency Analysis

Description: Avg. Disk sec/Read is the average time, in seconds, of a read of data to the disk. This analysis determines if any of the physical disks are responding slowly.

If the response times are greater than .015 (15 milliseconds), then the disk subsystem is keeping up with demand, but does not have much overhead left.

If the response times are greater than .025 (25 milliseconds), then noticeable slow downs and performance issues affecting users may be occurring.

Reference:
Ruling Out Disk-Bound Problems
http://technet.microsoft.com/en-us/library/5bcdd349-dcc6-43eb-9dc3-54175f7061ad.aspx


\PhysicalDisk(*)\Avg. Disk sec/Read

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read00.0350.5290.4190.0290.0320.0320.033
\\DB04\PhysicalDisk(1 P:)\Avg. Disk sec/Read00.0020.0070.0070.0010.0020.0020.003
\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read00.0370.5290.4220.030.0340.0340.035
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
12/16/2009 1:04:28 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0070.0270.0844.218
12/16/2009 1:04:47 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read00.0720.216.419
12/16/2009 1:06:41 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read00.0260.0570.514
12/16/2009 1:07:00 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read00.150.5293.07
12/16/2009 1:07:19 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0320.050.0610.875
12/16/2009 1:07:38 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0140.0360.0610.545
12/16/2009 1:07:57 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0290.030.0310.401
12/16/2009 1:08:16 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.020.0290.0340.356
12/16/2009 1:08:35 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0280.0290.0310.341
12/16/2009 1:08:54 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0280.0320.0370.347
12/16/2009 1:09:13 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.030.0310.0320.315
12/16/2009 1:09:32 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0320.0350.0440.346
12/16/2009 1:09:51 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0320.0350.040.325
12/16/2009 1:10:10 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0340.0380.0490.341
12/16/2009 1:10:29 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0290.0340.040.283
12/16/2009 1:10:48 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.030.0330.0360.256
12/16/2009 1:11:07 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0340.0380.0420.288
12/16/2009 1:11:26 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0290.080.230.626
12/16/2009 1:11:45 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0320.0370.0430.255
12/16/2009 1:12:04 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0370.0370.0380.251
12/16/2009 1:12:23 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0280.0320.0350.199
12/16/2009 1:12:42 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.030.0350.0460.217
12/16/2009 1:13:01 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.030.0360.0430.211
12/16/2009 1:13:20 PMDisk responsiveness is very slow (spike of more than 25ms)\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0020.0120.030.047
12/16/2009 1:13:39 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read0.0090.0710.1330.419
12/16/2009 1:04:28 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0070.0310.14.982
12/16/2009 1:04:47 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read00.0930.2728.392
12/16/2009 1:06:41 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read00.0260.0590.525
12/16/2009 1:07:00 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read00.150.5293.074
12/16/2009 1:07:19 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0330.0520.0630.903
12/16/2009 1:07:38 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0180.0380.0610.573
12/16/2009 1:07:57 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0310.0310.0320.428
12/16/2009 1:08:16 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0210.030.0360.38
12/16/2009 1:08:35 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.030.0310.0330.359
12/16/2009 1:08:54 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0290.0330.0380.369
12/16/2009 1:09:13 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0310.0320.0330.334
12/16/2009 1:09:32 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0340.0370.0470.369
12/16/2009 1:09:51 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0330.0370.0420.346
12/16/2009 1:10:10 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0360.0410.0520.364
12/16/2009 1:10:29 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0310.0360.0430.303
12/16/2009 1:10:48 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0310.0350.0380.274
12/16/2009 1:11:07 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0360.040.0440.305
12/16/2009 1:11:26 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.030.0850.2460.668
12/16/2009 1:11:45 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0340.0390.0460.272
12/16/2009 1:12:04 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0390.040.0410.268
12/16/2009 1:12:23 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0290.0330.0360.21
12/16/2009 1:12:42 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0320.0370.0480.231
12/16/2009 1:13:01 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0310.0380.0460.225
12/16/2009 1:13:20 PMDisk responsiveness is very slow (spike of more than 25ms)\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read00.0110.0320.042
12/16/2009 1:13:39 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read0.0090.0710.1330.422
Back to the top

Physical Disk Write Latency Analysis

Description: Avg. Disk sec/Write is the average time, in seconds, of a write of data to the disk. This analysis determines if any of the physical disks are responding slowly.

If the response times are greater than .015 (15 milliseconds), then the disk subsystem is keeping up with demand, but does not have much overhead left.

If the response times are greater than .025 (25 milliseconds), then noticeable slow downs and performance issues affecting users may be occurring.

Reference:
Ruling Out Disk-Bound Problems
http://technet.microsoft.com/en-us/library/5bcdd349-dcc6-43eb-9dc3-54175f7061ad.aspx


\PhysicalDisk(*)\Avg. Disk sec/Write

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Write00.0020.0460.0760.0030.0020.0020.002
\\DB04\PhysicalDisk(1 P:)\Avg. Disk sec/Write000-0.0010---
\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Write00.0020.0460.0760.0030.0020.0020.002
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
12/16/2009 1:04:28 PMAverage disk responsiveness is slow - more than 15ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Write00.0130.0462.447
12/16/2009 1:13:39 PMAverage disk responsiveness is slow - more than 15ms\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Write0.0020.0120.0230.076
12/16/2009 1:04:28 PMAverage disk responsiveness is slow - more than 15ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Write00.0130.0462.446
12/16/2009 1:13:39 PMAverage disk responsiveness is slow - more than 15ms\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Write0.0020.0120.0230.076
Back to the top

Logical Disk Read Latency Analysis

Description: Avg. Disk sec/Read is the average time, in seconds, of a read of data to the disk. This analysis determines if any of the physical disks are responding slowly.

If the response times are greater than .015 (15 milliseconds), then the disk subsystem is keeping up with demand, but does not have much overhead left.

If the response times are greater than .025 (25 milliseconds), then noticeable slow downs and performance issues affecting users may be occurring.

Reference:
Ruling Out Disk-Bound Problems
http://technet.microsoft.com/en-us/library/5bcdd349-dcc6-43eb-9dc3-54175f7061ad.aspx


\LogicalDisk(*)\Avg. Disk sec/Read

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read00.0350.5290.4190.0290.0320.0320.033
\\DB04\LogicalDisk(P:)\Avg. Disk sec/Read00.0020.0070.0070.0010.0020.0020.003
\\DB04\LogicalDisk(T:)\Avg. Disk sec/Read000.012-0.0260.001---
\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read00.0431.2010.4030.0560.0330.0330.035
\\DB04\LogicalDisk(C:)\Avg. Disk sec/Read00.0050.302-0.0280.0180.0020.0010.001
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
12/16/2009 1:04:28 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0070.0270.0844.219
12/16/2009 1:04:47 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read00.0720.216.419
12/16/2009 1:06:41 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read00.0260.0570.514
12/16/2009 1:07:00 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read00.150.5293.07
12/16/2009 1:07:19 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0320.050.0610.875
12/16/2009 1:07:38 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0140.0360.0610.545
12/16/2009 1:07:57 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0290.030.0310.401
12/16/2009 1:08:16 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.020.0290.0340.356
12/16/2009 1:08:35 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0280.0290.0310.341
12/16/2009 1:08:54 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0280.0320.0370.347
12/16/2009 1:09:13 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.030.0310.0320.315
12/16/2009 1:09:32 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0320.0350.0440.347
12/16/2009 1:09:51 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0320.0350.040.325
12/16/2009 1:10:10 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0340.0380.0490.341
12/16/2009 1:10:29 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0290.0340.040.283
12/16/2009 1:10:48 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.030.0330.0360.256
12/16/2009 1:11:07 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0340.0380.0420.288
12/16/2009 1:11:26 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0290.080.230.626
12/16/2009 1:11:45 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0320.0370.0430.255
12/16/2009 1:12:04 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0370.0370.0380.251
12/16/2009 1:12:23 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0280.0320.0350.199
12/16/2009 1:12:42 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.030.0350.0460.217
12/16/2009 1:13:01 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.030.0360.0430.211
12/16/2009 1:13:20 PMDisk responsiveness is very slow (spike of more than 25ms)\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0020.0120.030.047
12/16/2009 1:13:39 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read0.0090.0710.1330.419
12/16/2009 1:04:28 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read00.3021.20155.937
12/16/2009 1:06:41 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read00.030.0710.528
12/16/2009 1:07:00 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read00.1510.5293.032
12/16/2009 1:07:19 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0350.0520.0630.853
12/16/2009 1:07:38 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0180.0380.0610.522
12/16/2009 1:07:57 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0310.0320.0320.383
12/16/2009 1:08:16 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0210.030.0360.337
12/16/2009 1:08:35 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.030.0310.0330.32
12/16/2009 1:08:54 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0290.0340.0390.333
12/16/2009 1:09:13 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0310.0330.0330.299
12/16/2009 1:09:32 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0340.0370.0470.336
12/16/2009 1:09:51 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0330.0370.0420.315
12/16/2009 1:10:10 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0360.0410.0520.334
12/16/2009 1:10:29 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0310.0360.0430.275
12/16/2009 1:10:48 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0310.0360.0390.256
12/16/2009 1:11:07 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0360.040.0440.28
12/16/2009 1:11:26 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.030.0850.2460.644
12/16/2009 1:11:45 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0340.0390.0460.249
12/16/2009 1:12:04 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0390.040.0410.246
12/16/2009 1:12:23 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0290.0330.0360.189
12/16/2009 1:12:42 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0330.0370.0480.212
12/16/2009 1:13:01 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0320.0380.0460.207
12/16/2009 1:13:20 PMDisk responsiveness is very slow (spike of more than 25ms)\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read00.0110.0320.023
12/16/2009 1:13:39 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read0.0090.0710.1330.403
12/16/2009 1:04:47 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(C:)\Avg. Disk sec/Read00.1030.3029.331
12/16/2009 1:09:13 PMDisk responsiveness is very slow (spike of more than 25ms)\\DB04\LogicalDisk(C:)\Avg. Disk sec/Read00.010.0310.071
Back to the top

Logical Disk Write Latency Analysis

Description: Avg. Disk sec/Write is the average time, in seconds, of a write of data to the disk. This analysis determines if any of the physical disks are responding slowly.

If the response times are greater than .015 (15 milliseconds), then the disk subsystem is keeping up with demand, but does not have much overhead left.

If the response times are greater than .025 (25 milliseconds), then noticeable slow downs and performance issues affecting users may be occurring.

Reference:
Ruling Out Disk-Bound Problems
http://technet.microsoft.com/en-us/library/5bcdd349-dcc6-43eb-9dc3-54175f7061ad.aspx


\LogicalDisk(*)\Avg. Disk sec/Write

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Write00.0020.0460.0760.0030.0020.0020.002
\\DB04\LogicalDisk(P:)\Avg. Disk sec/Write000-0.0010---
\\DB04\LogicalDisk(T:)\Avg. Disk sec/Write00.0040.1770.0910.010.0020.0020.002
\\DB04\LogicalDisk(S:)\Avg. Disk sec/Write00.0090.8910.1710.040.0010.0010.001
\\DB04\LogicalDisk(C:)\Avg. Disk sec/Write00.0020.0210.0330.0010.0010.0010.001
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
12/16/2009 1:04:28 PMDisk responsiveness is very slow (spike of more than 25ms)\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Write00.0130.0462.447
12/16/2009 1:04:47 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(T:)\Avg. Disk sec/Write00.060.1775.636
12/16/2009 1:13:39 PMDisk responsiveness is very slow (spike of more than 25ms)\\DB04\LogicalDisk(T:)\Avg. Disk sec/Write0.0030.0150.0270.091
12/16/2009 1:04:28 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Write00.2240.89142.495
12/16/2009 1:13:39 PMAverage disk responsiveness is very slow - more than 25ms\\DB04\LogicalDisk(S:)\Avg. Disk sec/Write00.0270.0550.171
Back to the top

Disk Free Space for a Kernel Dump

Description: The default setting of complete memory dumps (blue screens) is to purge all of the physical memory to the C: drive under the windows directory as a memory.dmp file. This analysis checks to make sure there is enough free disk space for the operating system to dump all memory to disk.

\LogicalDisk(C:)\Free Megabytes

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\LogicalDisk(C:)\Free Megabytes704741776-45536742743744
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
12/16/2009 1:04:09 PMNot enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes7767767760
12/16/2009 1:04:28 PMNot enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes7767767760
12/16/2009 1:04:47 PMNot enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes7767767760
12/16/2009 1:05:06 PMNot enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes7767767760
12/16/2009 1:05:25 PMNot enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes7767767760
12/16/2009 1:05:44 PMNot enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes7767767760
12/16/2009 1:06:03 PMNot enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes7767767760
12/16/2009 1:06:22 PMNot enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes7767767760
12/16/2009 1:06:41 PMNot enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes7767767760
12/16/2009 1:07:00 PMNot enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes7767767760
12/16/2009 1:07:19 PMNot enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes7767767760
12/16/2009 1:07:38 PMNot enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes7767767760
12/16/2009 1:07:57 PMNot enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes7767767760
12/16/2009 1:08:16 PMNot enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes7767767760
12/16/2009 1:08:35 PMNot enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes7767767760
12/16/2009 1:08:54 PMNot enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes704758776-227
12/16/2009 1:09:13 PMNot enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes704704704-853
12/16/2009 1:09:32 PMNot enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes704704704-802
12/16/2009 1:09:51 PMNot enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes704704704-758
12/16/2009 1:10:10 PMNot enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes704704704-718
12/16/2009 1:10:29 PMNot enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes704704704-682
12/16/2009 1:10:48 PMNot enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes704704704-650
12/16/2009 1:11:07 PMNot enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes704704704-620
12/16/2009 1:11:26 PMNot enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes704704704-593
12/16/2009 1:11:45 PMNot enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes704704704-568
12/16/2009 1:12:04 PMNot enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes704704704-546
12/16/2009 1:12:23 PMNot enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes704704704-525
12/16/2009 1:12:42 PMNot enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes704704704-505
12/16/2009 1:13:01 PMNot enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes704704704-487
12/16/2009 1:13:20 PMNot enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes704704704-470
12/16/2009 1:13:39 PMNot enough disk space on C: drive for a kernel dump (blue screen)\\DB04\LogicalDisk(C:)\Free Megabytes704704704-455
Back to the top

Process IO Data Operations/sec

Description: The rate at which the process is issuing read and write I/O operations. This counter counts all I/O activity generated by the process to include file, network and device I/Os.

\Process(*)\IO Data Operations/sec

\Process(*)\IO Data Operations/sec

\Process(*)\IO Data Operations/sec

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\Process(_Total)\IO Data Operations/sec51803,908-12,892457665655
\\DB04\Process(dfrgifc)\IO Data Operations/sec023-0---
\\DB04\Process(powershell#4)\IO Data Operations/sec--------
\\DB04\Process(cmd#4)\IO Data Operations/sec--------
\\DB04\Process(powershell#3)\IO Data Operations/sec--------
\\DB04\Process(cmd#3)\IO Data Operations/sec--------
\\DB04\Process(powershell#2)\IO Data Operations/sec00130000
\\DB04\Process(cmd#2)\IO Data Operations/sec0-000---
\\DB04\Process(SQLCMD#1)\IO Data Operations/sec--------
\\DB04\Process(SQLCMD)\IO Data Operations/sec013147391612105
\\DB04\Process(msinfo32)\IO Data Operations/sec0-000---
\\DB04\Process(cmd#1)\IO Data Operations/sec0-000---
\\DB04\Process(SQLdiag)\IO Data Operations/sec012-30111
\\DB04\Process(powershell#1)\IO Data Operations/sec0-000---
\\DB04\Process(cmd)\IO Data Operations/sec0-000---
\\DB04\Process(explorer#1)\IO Data Operations/sec0-000---
\\DB04\Process(svchost#8)\IO Data Operations/sec00000000
\\DB04\Process(SQLAGENT)\IO Data Operations/sec01200111
\\DB04\Process(fdhost)\IO Data Operations/sec0-000---
\\DB04\Process(sqlservr)\IO Data Operations/sec02135041020191718
\\DB04\Process(Ssms)\IO Data Operations/sec01220111
\\DB04\Process(wpabaln)\IO Data Operations/sec0-000---
\\DB04\Process(powershell)\IO Data Operations/sec0-000---
\\DB04\Process(wmiprvse#1)\IO Data Operations/sec0-000---
\\DB04\Process(explorer)\IO Data Operations/sec0-000---
\\DB04\Process(wmiprvse)\IO Data Operations/sec0611,898-6,587221511
\\DB04\Process(alg)\IO Data Operations/sec00000000
\\DB04\Process(fdlauncher)\IO Data Operations/sec00000000
\\DB04\Process(svchost#7)\IO Data Operations/sec00200000
\\DB04\Process(sqlwriter)\IO Data Operations/sec00000000
\\DB04\Process(svchost#6)\IO Data Operations/sec00000000
\\DB04\Process(MsDtsSrvr)\IO Data Operations/sec00000000
\\DB04\Process(svchost#5)\IO Data Operations/sec00000000
\\DB04\Process(msdtc)\IO Data Operations/sec00000000
\\DB04\Process(vmicsvc#4)\IO Data Operations/sec00000000
\\DB04\Process(vmicsvc#3)\IO Data Operations/sec11100111
\\DB04\Process(vmicsvc#2)\IO Data Operations/sec00000000
\\DB04\Process(vmicsvc#1)\IO Data Operations/sec00000000
\\DB04\Process(vmicsvc)\IO Data Operations/sec11210111
\\DB04\Process(spoolsv)\IO Data Operations/sec00000000
\\DB04\Process(svchost#4)\IO Data Operations/sec2898-2256777
\\DB04\Process(svchost#3)\IO Data Operations/sec00110000
\\DB04\Process(svchost#2)\IO Data Operations/sec00110000
\\DB04\Process(svchost#1)\IO Data Operations/sec00000000
\\DB04\Process(svchost)\IO Data Operations/sec00000000
\\DB04\Process(lsass)\IO Data Operations/sec0671,978-6,905234822
\\DB04\Process(services)\IO Data Operations/sec0113-413100
\\DB04\Process(winlogon)\IO Data Operations/sec0-000---
\\DB04\Process(csrss)\IO Data Operations/sec0019-4720--
\\DB04\Process(smss)\IO Data Operations/sec0-000---
\\DB04\Process(System)\IO Data Operations/sec002-50000
\\DB04\Process(Idle)\IO Data Operations/sec0-000---
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
*OK\\DB04\Process(dfrgifc)\IO Data Operations/sec023-
*OK\\DB04\Process(powershell#4)\IO Data Operations/sec----
*OK\\DB04\Process(cmd#4)\IO Data Operations/sec----
*OK\\DB04\Process(powershell#3)\IO Data Operations/sec----
*OK\\DB04\Process(cmd#3)\IO Data Operations/sec----
*OK\\DB04\Process(powershell#2)\IO Data Operations/sec0013
*OK\\DB04\Process(cmd#2)\IO Data Operations/sec0-00
*OK\\DB04\Process(SQLCMD#1)\IO Data Operations/sec----
*OK\\DB04\Process(SQLCMD)\IO Data Operations/sec01314739
*OK\\DB04\Process(msinfo32)\IO Data Operations/sec0-00
*OK\\DB04\Process(cmd#1)\IO Data Operations/sec0-00
*OK\\DB04\Process(SQLdiag)\IO Data Operations/sec012-3
*OK\\DB04\Process(powershell#1)\IO Data Operations/sec0-00
*OK\\DB04\Process(cmd)\IO Data Operations/sec0-00
*OK\\DB04\Process(explorer#1)\IO Data Operations/sec0-00
*OK\\DB04\Process(svchost#8)\IO Data Operations/sec0000
*OK\\DB04\Process(SQLAGENT)\IO Data Operations/sec0120
*OK\\DB04\Process(fdhost)\IO Data Operations/sec0-00
*OK\\DB04\Process(sqlservr)\IO Data Operations/sec021350410
*OK\\DB04\Process(Ssms)\IO Data Operations/sec0122
*OK\\DB04\Process(wpabaln)\IO Data Operations/sec0-00
*OK\\DB04\Process(powershell)\IO Data Operations/sec0-00
*OK\\DB04\Process(wmiprvse#1)\IO Data Operations/sec0-00
*OK\\DB04\Process(explorer)\IO Data Operations/sec0-00
12/16/2009 1:04:09 PMThis process is using more than 1000 data I/O's per second\\DB04\Process(wmiprvse)\IO Data Operations/sec1121,0441,8980
12/16/2009 1:04:09 PMThis process is using more than 1000 data I/O's per second\\DB04\Process(lsass)\IO Data Operations/sec1491,0951,9780
Back to the top

Process IO Other Operations/sec

Description: The rate at which the process is issuing I/O operations that are neither read nor write operations (for example, a control function). This counter counts all I/O activity generated by the process to include file, network and device I/Os.

\Process(*)\IO Other Operations/sec

\Process(*)\IO Other Operations/sec

\Process(*)\IO Other Operations/sec

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\Process(_Total)\IO Other Operations/sec251763,463-13,752459633937
\\DB04\Process(dfrgifc)\IO Other Operations/sec01122-0---
\\DB04\Process(powershell#4)\IO Other Operations/sec--------
\\DB04\Process(cmd#4)\IO Other Operations/sec--------
\\DB04\Process(powershell#3)\IO Other Operations/sec--------
\\DB04\Process(cmd#3)\IO Other Operations/sec--------
\\DB04\Process(powershell#2)\IO Other Operations/sec02580221
\\DB04\Process(cmd#2)\IO Other Operations/sec0-000---
\\DB04\Process(SQLCMD#1)\IO Other Operations/sec--------
\\DB04\Process(SQLCMD)\IO Other Operations/sec00000---
\\DB04\Process(msinfo32)\IO Other Operations/sec0-000---
\\DB04\Process(cmd#1)\IO Other Operations/sec0-000---
\\DB04\Process(SQLdiag)\IO Other Operations/sec81619-231161616
\\DB04\Process(powershell#1)\IO Other Operations/sec00000---
\\DB04\Process(cmd)\IO Other Operations/sec0-000---
\\DB04\Process(explorer#1)\IO Other Operations/sec0019-4110--
\\DB04\Process(svchost#8)\IO Other Operations/sec0-000---
\\DB04\Process(SQLAGENT)\IO Other Operations/sec71013-60101010
\\DB04\Process(fdhost)\IO Other Operations/sec0-000---
\\DB04\Process(sqlservr)\IO Other Operations/sec06117-3416310
\\DB04\Process(Ssms)\IO Other Operations/sec001-10---
\\DB04\Process(wpabaln)\IO Other Operations/sec0-000---
\\DB04\Process(powershell)\IO Other Operations/sec0-000---
\\DB04\Process(wmiprvse#1)\IO Other Operations/sec0-000---
\\DB04\Process(explorer)\IO Other Operations/sec003-30000
\\DB04\Process(wmiprvse)\IO Other Operations/sec0581,163-5,5001801600
\\DB04\Process(alg)\IO Other Operations/sec0-000---
\\DB04\Process(fdlauncher)\IO Other Operations/sec0-000---
\\DB04\Process(svchost#7)\IO Other Operations/sec00100---
\\DB04\Process(sqlwriter)\IO Other Operations/sec0-000---
\\DB04\Process(svchost#6)\IO Other Operations/sec0-000---
\\DB04\Process(MsDtsSrvr)\IO Other Operations/sec0-000---
\\DB04\Process(svchost#5)\IO Other Operations/sec0-000---
\\DB04\Process(msdtc)\IO Other Operations/sec0-000---
\\DB04\Process(vmicsvc#4)\IO Other Operations/sec0-000---
\\DB04\Process(vmicsvc#3)\IO Other Operations/sec0-000---
\\DB04\Process(vmicsvc#2)\IO Other Operations/sec0-000---
\\DB04\Process(vmicsvc#1)\IO Other Operations/sec0-000---
\\DB04\Process(vmicsvc)\IO Other Operations/sec0-000---
\\DB04\Process(spoolsv)\IO Other Operations/sec0-000---
\\DB04\Process(svchost#4)\IO Other Operations/sec05297-78422110
\\DB04\Process(svchost#3)\IO Other Operations/sec00310000
\\DB04\Process(svchost#2)\IO Other Operations/sec001001---
\\DB04\Process(svchost#1)\IO Other Operations/sec008-1810--
\\DB04\Process(svchost)\IO Other Operations/sec006-130---
\\DB04\Process(lsass)\IO Other Operations/sec0772,279-7,962270821
\\DB04\Process(services)\IO Other Operations/sec0511-21555
\\DB04\Process(winlogon)\IO Other Operations/sec001-200--
\\DB04\Process(csrss)\IO Other Operations/sec0169-1464---
\\DB04\Process(smss)\IO Other Operations/sec0-000---
\\DB04\Process(System)\IO Other Operations/sec019-91000
\\DB04\Process(Idle)\IO Other Operations/sec0-000---
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
*OK\\DB04\Process(dfrgifc)\IO Other Operations/sec01122-
*OK\\DB04\Process(powershell#4)\IO Other Operations/sec----
*OK\\DB04\Process(cmd#4)\IO Other Operations/sec----
*OK\\DB04\Process(powershell#3)\IO Other Operations/sec----
*OK\\DB04\Process(cmd#3)\IO Other Operations/sec----
*OK\\DB04\Process(powershell#2)\IO Other Operations/sec0258
*OK\\DB04\Process(cmd#2)\IO Other Operations/sec0-00
*OK\\DB04\Process(SQLCMD#1)\IO Other Operations/sec----
*OK\\DB04\Process(SQLCMD)\IO Other Operations/sec0000
*OK\\DB04\Process(msinfo32)\IO Other Operations/sec0-00
*OK\\DB04\Process(cmd#1)\IO Other Operations/sec0-00
*OK\\DB04\Process(SQLdiag)\IO Other Operations/sec81619-23
*OK\\DB04\Process(powershell#1)\IO Other Operations/sec0000
*OK\\DB04\Process(cmd)\IO Other Operations/sec0-00
*OK\\DB04\Process(explorer#1)\IO Other Operations/sec0019-41
*OK\\DB04\Process(svchost#8)\IO Other Operations/sec0-00
*OK\\DB04\Process(SQLAGENT)\IO Other Operations/sec71013-6
*OK\\DB04\Process(fdhost)\IO Other Operations/sec0-00
*OK\\DB04\Process(sqlservr)\IO Other Operations/sec06117-34
*OK\\DB04\Process(Ssms)\IO Other Operations/sec001-1
*OK\\DB04\Process(wpabaln)\IO Other Operations/sec0-00
*OK\\DB04\Process(powershell)\IO Other Operations/sec0-00
*OK\\DB04\Process(wmiprvse#1)\IO Other Operations/sec0-00
*OK\\DB04\Process(explorer)\IO Other Operations/sec003-3
*OK\\DB04\Process(wmiprvse)\IO Other Operations/sec0581,163-5,500
*OK\\DB04\Process(alg)\IO Other Operations/sec0-00
*OK\\DB04\Process(fdlauncher)\IO Other Operations/sec0-00
*OK\\DB04\Process(svchost#7)\IO Other Operations/sec0010
*OK\\DB04\Process(sqlwriter)\IO Other Operations/sec0-00
*OK\\DB04\Process(svchost#6)\IO Other Operations/sec0-00
*OK\\DB04\Process(MsDtsSrvr)\IO Other Operations/sec0-00
*OK\\DB04\Process(svchost#5)\IO Other Operations/sec0-00
*OK\\DB04\Process(msdtc)\IO Other Operations/sec0-00
*OK\\DB04\Process(vmicsvc#4)\IO Other Operations/sec0-00
*OK\\DB04\Process(vmicsvc#3)\IO Other Operations/sec0-00
*OK\\DB04\Process(vmicsvc#2)\IO Other Operations/sec0-00
*OK\\DB04\Process(vmicsvc#1)\IO Other Operations/sec0-00
*OK\\DB04\Process(vmicsvc)\IO Other Operations/sec0-00
*OK\\DB04\Process(spoolsv)\IO Other Operations/sec0-00
*OK\\DB04\Process(svchost#4)\IO Other Operations/sec05297-784
*OK\\DB04\Process(svchost#3)\IO Other Operations/sec0031
*OK\\DB04\Process(svchost#2)\IO Other Operations/sec00100
*OK\\DB04\Process(svchost#1)\IO Other Operations/sec008-18
*OK\\DB04\Process(svchost)\IO Other Operations/sec006-13
12/16/2009 1:04:09 PMThis process is using more than 1000 other I/O's per second\\DB04\Process(lsass)\IO Other Operations/sec1741,2622,2790
Back to the top

LogicalDisk Disk Transfers/sec

Description: Disk Transfers/sec is the rate of read and write operations on the disk.

\LogicalDisk(*)\Disk Transfers/sec

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\LogicalDisk(_Total)\Disk Transfers/sec129362-39330242121
\\DB04\LogicalDisk(P:)\Disk Transfers/sec016-120111
\\DB04\LogicalDisk(T:)\Disk Transfers/sec0110251111
\\DB04\LogicalDisk(S:)\Disk Transfers/sec01432635718111010
\\DB04\LogicalDisk(C:)\Disk Transfers/sec113303-76322888
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
12/16/2009 1:07:00 PMLess than 80 I/O's per second on average when disk latency is longer than 25ms. This may indicate too many virtual LUNs using the same physical disks on a SAN. This was a spike - not an average.\\DB04\LogicalDisk(_Total)\Disk Transfers/sec91722-2,641
12/16/2009 1:07:00 PMLess than 80 I/O's per second on average when disk latency is longer than 25ms. This may indicate too many virtual LUNs using the same physical disks on a SAN. This was a spike - not an average.\\DB04\LogicalDisk(S:)\Disk Transfers/sec059-34
Back to the top

Memory


Free System Page Table Entries

Description: Free System Page Table Entries is the number of page table entries not currently in used by the system. This analysis determines if the system is running out of free system page table entries (PTEs) by checking if there is less than 5,000 free PTE’s with a Warning if there is less than 10,000 free PTE’s. Lack of enough PTEs can result in system wide hangs. Also note that the /3GB switch will lower the amount of free PTEs significantly.

The Performance Monitor “Memory\Free System Page Table Entries” counter is inaccurate on installations of Windows Server 2003 without Service Pack 1. For more information about this counter, see Microsoft Knowledge Base article 894067 “The Performance tool does not accurately show the available Free System Page Table entries in Windows Server 2003” http://go.microsoft.com/fwlink/?linkid=3052&kbid=894067

Fix for Win2003 SP1 systems with /3GB and low on PTE’s: If the system is low on PTE’s, running Windows 2003, and using /3GB switch, then consider using the /USERVA switch to give back some of the memory to the kernel. Note, this only works for Free System PTE issues.

For more information on the USERVA switch, go to: How to use the /userva switch with the /3GB switch to tune the User-mode space to a value between 2 GB and 3 GB http://support.microsoft.com/kb/316739

Reference:
Ruling Out Memory-Bound Problems
http://technet.microsoft.com/en-us/library/7a44b064-8872-4edf-aac7-36b2a17f662a.aspx

Microsoft Knowledge Base article 894067 “The Performance tool does not accurately show the available Free System Page Table entries in Windows Server 2003” http://go.microsoft.com/fwlink/?linkid=3052&kbid=894067

“How to use the /userva switch with the /3GB switch to tune the User-mode space to a value between 2 GB and 3 GB” http://support.microsoft.com/kb/316739">http://support.microsoft.com/kb/316739

How to determine the appropriate page file size for 64-bit versions of Windows Server 2003 or Windows XP
http://support.microsoft.com/kb/889654

\Memory\Free System Page Table Entries

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\Memory\Free System Page Table Entries2,081,7092,081,7092,081,709002,081,7092,081,7092,081,709
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
*OK\\DB04\Memory\Free System Page Table Entries2,081,7092,081,7092,081,7090
Back to the top

Pool Non Paged Bytes

Description: Pool Nonpaged Bytes is the size, in bytes, of the nonpaged pool, an area of system memory (physical memory used by the operating system) for objects that cannot be written to disk, but must remain in physical memory as long as they are allocated.

This analysis checks to see if the system is becoming close to the maximum Pool Nonpaged memory size. It does this by estimating the pool sizes taking into consideration /3GB, physical memory size, and 32-bit/64-bit, then determining if the value is higher than 60% of the estimated pool size. If the system becomes close to the maximum size, then the system could experience system wide hangs. Checks both 32-bit and 64-bit memory pools. Warning: The /3GB switch option in the boot.ini file significantly reduces the size of this memory pool.

If the system is low on Paged Pool or non-Paged pool memory, then it is recommended to open a support case with Microsoft to address this. Alternatively, you can use a free and public tool called Poolmon.exe to see what DLL’s are using kernel memory (see the article below). Most kernel memory leaks can be tracked back to a usermode process. To identify which user mode process is responsible, reboot the system (so you start off with a clean system), start a performance monitor log intending to run for a week or more capturing the Memory and Process objects, then analyze the perfmon log looking for memory leaks and/or handle leaks in one or more of the processes. In any case, migrating to a 64-bit version of Windows should alleviate this issue.
References:
How to Use Memory Pool Monitor (Poolmon.exe) to Troubleshoot Kernel Mode Memory Leaks
http://support.microsoft.com/kb/177415

Ruling Out Memory-Bound Problems
http://technet.microsoft.com/en-us/library/7a44b064-8872-4edf-aac7-36b2a17f662a.aspx

How to determine the appropriate page file size for 64-bit versions of Windows Server 2003 or Windows XP
http://support.microsoft.com/kb/889654

\Memory\Pool Nonpaged Bytes

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\Memory\Pool Nonpaged Bytes22,511,61622,556,22122,757,376-258,69528,99422,554,40122,551,77422,551,040
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
*OK\\DB04\Memory\Pool Nonpaged Bytes22,511,61622,556,22122,757,376-258,695
Back to the top

Pool Paged Bytes

Description: This analysis checks to see if the system is becoming close to the maximum Pool paged memory size. Pool Paged Bytes is the size, in bytes, of the paged pool, an area of system memory (physical memory used by the operating system) for objects that can be written to disk when they are not being used.

This analysis checks to see if the system is becoming close to the maximum Pool Paged memory size. It does this by estimating the pool sizes taking into consideration /3GB, physical memory size, and 32-bit/64-bit, then determining if the value is higher than 60% of the estimated pool size. If the system becomes close to the maximum size, then the system could experience system wide hangs. Checks both 32-bit and 64-bit memory pools. Warning: The /3GB switch option in the boot.ini file significantly reduces the size of this memory pool.

If the system is low on Paged Pool or non-Paged pool memory, then it is recommended to open a support case with Microsoft to address this. Alternatively, you can use a free and public tool called Poolmon.exe to see what DLL’s are using kernel memory (see the article below). Most kernel memory leaks can be tracked back to a usermode process. To identify which user mode process is responsible, reboot the system (so you start off with a clean system), start a performance monitor log intending to run for a week or more capturing the Memory and Process objects, then analyze the perfmon log looking for memory leaks and/or handle leaks in one or more of the processes. In any case, migrating to a 64-bit version of Windows should alleviate this issue.

Reference:
How to Use Memory Pool Monitor (Poolmon.exe) to Troubleshoot Kernel Mode Memory Leaks
http://support.microsoft.com/kb/177415

Ruling Out Memory-Bound Problems
http://technet.microsoft.com/en-us/library/7a44b064-8872-4edf-aac7-36b2a17f662a.aspx

How to determine the appropriate page file size for 64-bit versions of Windows Server 2003 or Windows XP
http://support.microsoft.com/kb/889654

\Memory\Pool Paged Bytes

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\Memory\Pool Paged Bytes46,542,84846,675,13150,315,264-11,725,339406,35846,588,31146,548,65146,546,749
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
*OK\\DB04\Memory\Pool Paged Bytes46,542,84846,675,13150,315,264-11,725,339
Back to the top

Available Memory

Description: Available MBytes is the amount of physical memory available to processes running on the computer, in Megabytes, rather than bytes as reported in Memory\Available Bytes. The Virtual Memory Manager continually adjusts the space used in physical memory and on disk to maintain a minimum number of available bytes for the operating system and processes. When available bytes are plentiful, the Virtual Memory Manager lets the working sets of processes grow, or keeps them stable by removing an old page for each new page added. When available bytes are few, the Virtual Memory Manager must trim the working sets of processes to maintain the minimum required. This analysis checks to see if the total available memory is low – Warning at 10% available and Critical at 5% available. A Warning is also alerted when a decreasing trend of 10MB’s per hour is detecting indicating a potential upcoming memory condition. Low physical memory can cause increased privileged mode CPU and system delays.

Reference:
Ruling Out Memory-Bound Problems
http://technet.microsoft.com/en-us/library/7a44b064-8872-4edf-aac7-36b2a17f662a.aspx

Detecting Memory Bottlenecks
http://www.microsoft.com/resources/documentation/windowsnt/4/workstation/reskit/en-us/04memory.mspx?mfr=true

\Memory\Available MBytes

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\Memory\Available MBytes4110613126516106105103
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
12/16/2009 1:04:09 PMVery low on available memory - less than 5% available\\DB04\Memory\Available MBytes4173860
12/16/2009 1:04:28 PMVery low on available memory - less than 5% available\\DB04\Memory\Available MBytes811001185,211
12/16/2009 1:04:47 PMLow on available memory - less than 10% available\\DB04\Memory\Available MBytes1171191214,389
12/16/2009 1:05:06 PMLow on available memory - less than 10% available\\DB04\Memory\Available MBytes1311311313,663
12/16/2009 1:05:25 PMLow on available memory - less than 10% available\\DB04\Memory\Available MBytes1311311312,747
12/16/2009 1:05:44 PMLow on available memory - less than 10% available\\DB04\Memory\Available MBytes1311311312,198
12/16/2009 1:06:03 PMLow on available memory - less than 10% available\\DB04\Memory\Available MBytes1311311311,832
12/16/2009 1:06:22 PMLow on available memory - less than 10% available\\DB04\Memory\Available MBytes1311311311,570
12/16/2009 1:06:41 PMLow on available memory - less than 10% available\\DB04\Memory\Available MBytes1281291311,320
12/16/2009 1:07:00 PMLow on available memory - less than 10% available\\DB04\Memory\Available MBytes1171231281,047
12/16/2009 1:07:19 PMLow on available memory - less than 10% available\\DB04\Memory\Available MBytes117117117834
12/16/2009 1:07:38 PMLow on available memory - less than 10% available\\DB04\Memory\Available MBytes117117117758
12/16/2009 1:07:57 PMLow on available memory - less than 10% available\\DB04\Memory\Available MBytes116116117683
12/16/2009 1:08:16 PMVery low on available memory - less than 5% available\\DB04\Memory\Available MBytes97111116557
12/16/2009 1:08:35 PMVery low on available memory - less than 5% available\\DB04\Memory\Available MBytes939494281
12/16/2009 1:08:54 PMVery low on available memory - less than 5% available\\DB04\Memory\Available MBytes949494265
12/16/2009 1:09:13 PMVery low on available memory - less than 5% available\\DB04\Memory\Available MBytes949494249
12/16/2009 1:09:32 PMVery low on available memory - less than 5% available\\DB04\Memory\Available MBytes939494231
12/16/2009 1:09:51 PMVery low on available memory - less than 5% available\\DB04\Memory\Available MBytes939393211
12/16/2009 1:10:10 PMVery low on available memory - less than 5% available\\DB04\Memory\Available MBytes939393199
12/16/2009 1:10:29 PMVery low on available memory - less than 5% available\\DB04\Memory\Available MBytes939393189
12/16/2009 1:10:48 PMVery low on available memory - less than 5% available\\DB04\Memory\Available MBytes929395180
12/16/2009 1:11:07 PMVery low on available memory - less than 5% available\\DB04\Memory\Available MBytes949495185
12/16/2009 1:11:26 PMVery low on available memory - less than 5% available\\DB04\Memory\Available MBytes949494173
12/16/2009 1:11:45 PMVery low on available memory - less than 5% available\\DB04\Memory\Available MBytes949494166
12/16/2009 1:12:04 PMVery low on available memory - less than 5% available\\DB04\Memory\Available MBytes949494159
12/16/2009 1:12:23 PMVery low on available memory - less than 5% available\\DB04\Memory\Available MBytes949494153
12/16/2009 1:12:42 PMVery low on available memory - less than 5% available\\DB04\Memory\Available MBytes949596154
12/16/2009 1:13:01 PMVery low on available memory - less than 5% available\\DB04\Memory\Available MBytes979797162
12/16/2009 1:13:20 PMVery low on available memory - less than 5% available\\DB04\Memory\Available MBytes9799103170
12/16/2009 1:13:39 PMLow on available memory - less than 10% available\\DB04\Memory\Available MBytes115115115265
Back to the top

Memory Pages/sec

Description: This analysis checks to see if the Pages/sec is high. If it is high, then the system is likely running out of memory by trying to page the memory to the disk. Pages/sec is the rate at which pages are read from or written to disk to resolve hard page faults. This counter is a primary indicator of the kinds of faults that cause system-wide delays. It is the sum of Memory\Pages Input/sec and Memory\Pages Output/sec. It is counted in numbers of pages, so it can be compared to other counts of pages, such as Memory\Page Faults/sec, without conversion. It includes pages retrieved to satisfy faults in the file system cache (usually requested by applications) non-cached mapped memory files.

This counter should always be below 1000, therefore this analysis checks for values above 1000. Use this analysis in correlation with Available Memory Analysis and Memory Leak Analysis. All are throwing alerts at the same time, then this may indicate the system is running out of memory and the suspected processes involved and follow analysis steps mentioned in the Memory Leak analysis.

Reference:
Ruling Out Memory-Bound Problems
http://technet.microsoft.com/en-us/library/7a44b064-8872-4edf-aac7-36b2a17f662a.aspx


\Memory\Pages/sec

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\Memory\Pages/sec013259-1,20442200
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
*OK\\DB04\Memory\Pages/sec013259-1,204
Back to the top

Memory Leak Detection

Description: This analysis determines if any of the processes are consuming a large size of the system's memory and if the process is increasing in memory consumption over time. A process consuming large portions of memory is okay as long as the process returns the memory back to the system. Look for increasing trends in the chart. An increasing trend over a long period of time could indicate a memory leak. Private Bytes is the current size, in bytes, of memory that this process has allocated that cannot be shared with other processes. This analysis checks for a 10MB’s per hour and 5MB’s per hour increasing trends. Use this analysis in correlation with the Available Memory analysis.

Also, keep in mind that newly started processes will initially appear as a memory leak when it is simply normal start up behavior. A memory leak is when a process continues to consume memory and not releasing memory over a long period of time.

Use this analysis in correlation with the Available Memory analysis. If you suspect a memory leak condition, then install and use the Debug Diag tool. For more information on the Debug Diag Tool, see the references section.

References:

Debug Diagnostic Tool v1.1 http://www.microsoft.com/downloads/details.aspx?FamilyID=28bd5941-c458-46f1-b24d-f60151d875a3&displaylang=en

\Process(*)\Private Bytes

\Process(*)\Private Bytes

\Process(*)\Private Bytes

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\Process(_Total)\Private Bytes2,049,900,5442,119,122,1292,203,430,9123,621,72635,631,5902,124,755,2722,131,425,3142,136,269,385
\\DB04\Process(dfrgifc)\Private Bytes1,515,5201,650,6881,732,608-0---
\\DB04\Process(powershell#4)\Private Bytes52,613,12052,613,12052,613,120-0---
\\DB04\Process(cmd#4)\Private Bytes1,978,3681,978,3681,978,368-0---
\\DB04\Process(powershell#3)\Private Bytes50,417,66450,417,66450,417,664-0---
\\DB04\Process(cmd#3)\Private Bytes1,978,3681,978,3681,978,368-0---
\\DB04\Process(powershell#2)\Private Bytes51,720,19253,468,67855,861,24814,687,3941,181,57953,486,89453,444,23353,411,255
\\DB04\Process(cmd#2)\Private Bytes1,978,3681,978,3681,978,368001,978,3681,978,3681,978,368
\\DB04\Process(SQLCMD#1)\Private Bytes4,366,3364,366,3364,366,336-0---
\\DB04\Process(SQLCMD)\Private Bytes4,878,3364,908,2964,935,680-232,82513,3134,907,9144,905,7284,903,424
\\DB04\Process(msinfo32)\Private Bytes4,231,1687,749,7469,240,576262,154,7791,176,1317,749,7468,557,2278,557,227
\\DB04\Process(cmd#1)\Private Bytes1,978,3682,157,5353,829,760-11,693,002547,3642,049,5751,978,3681,978,368
\\DB04\Process(SQLdiag)\Private Bytes16,678,91216,891,47516,945,152866,62748,07116,895,13416,894,05416,891,465
\\DB04\Process(powershell#1)\Private Bytes52,850,68852,867,53452,899,840-310,43419,61452,866,99352,864,51252,862,098
\\DB04\Process(cmd)\Private Bytes1,974,2721,974,2721,974,272001,974,2721,974,2721,974,272
\\DB04\Process(explorer#1)\Private Bytes7,897,0887,947,0338,044,544-931,30147,5597,945,2957,944,0907,948,434
\\DB04\Process(svchost#8)\Private Bytes3,960,8323,960,8323,960,832003,960,8323,960,8323,960,832
\\DB04\Process(SQLAGENT)\Private Bytes24,678,40024,813,17224,817,664879,56224,60624,817,66424,817,66424,817,664
\\DB04\Process(fdhost)\Private Bytes5,095,4245,143,7835,144,57603,0195,144,5765,144,5765,144,576
\\DB04\Process(sqlservr)\Private Bytes1,441,280,0001,508,957,2831,538,826,240270,930,99837,566,2741,514,361,7771,520,990,1061,527,363,218
\\DB04\Process(Ssms)\Private Bytes196,517,888196,620,585196,694,016898,96469,384196,626,786196,633,037196,637,550
\\DB04\Process(wpabaln)\Private Bytes1,257,4721,257,4721,257,472001,257,4721,257,4721,257,472
\\DB04\Process(powershell)\Private Bytes34,664,44834,664,44834,664,4480034,664,44834,664,44834,664,448
\\DB04\Process(wmiprvse#1)\Private Bytes2,936,8322,936,8322,936,832002,936,8322,936,8322,936,832
\\DB04\Process(explorer)\Private Bytes10,997,76011,039,97511,071,488-465,65136,02011,042,42211,044,76211,049,106
\\DB04\Process(wmiprvse)\Private Bytes21,368,83223,953,81529,921,280-19,938,897744,94823,914,77223,916,61223,995,051
\\DB04\Process(alg)\Private Bytes1,425,4081,425,4081,425,408001,425,4081,425,4081,425,408
\\DB04\Process(fdlauncher)\Private Bytes1,191,9361,191,9361,191,936001,191,9361,191,9361,191,936
\\DB04\Process(svchost#7)\Private Bytes2,670,5922,748,9452,768,896-310,43437,1752,756,4502,765,8242,768,896
\\DB04\Process(sqlwriter)\Private Bytes1,949,6961,949,6961,949,696001,949,6961,949,6961,949,696
\\DB04\Process(svchost#6)\Private Bytes917,504917,504917,50400917,504917,504917,504
\\DB04\Process(MsDtsSrvr)\Private Bytes50,216,96050,216,96050,216,9600050,216,96050,216,96050,216,960
\\DB04\Process(svchost#5)\Private Bytes1,134,5921,134,5921,134,592001,134,5921,134,5921,134,592
\\DB04\Process(msdtc)\Private Bytes2,695,1682,695,1682,695,168002,695,1682,695,1682,695,168
\\DB04\Process(vmicsvc#4)\Private Bytes3,207,1683,207,1683,207,168003,207,1683,207,1683,207,168
\\DB04\Process(vmicsvc#3)\Private Bytes3,137,5363,137,5363,137,536003,137,5363,137,5363,137,536
\\DB04\Process(vmicsvc#2)\Private Bytes3,121,1523,121,1523,121,152003,121,1523,121,1523,121,152
\\DB04\Process(vmicsvc#1)\Private Bytes8,728,5768,728,5768,728,576008,728,5768,728,5768,728,576
\\DB04\Process(vmicsvc)\Private Bytes4,042,7524,042,7524,042,752004,042,7524,042,7524,042,752
\\DB04\Process(spoolsv)\Private Bytes5,046,2725,154,7945,177,344-827,82348,2085,165,5815,177,3445,177,344
\\DB04\Process(svchost#4)\Private Bytes27,455,48828,915,94333,697,792-14,060,0591,131,96428,945,21128,950,78428,968,667
\\DB04\Process(svchost#3)\Private Bytes2,371,5842,374,3592,420,736-310,43410,6802,371,5842,371,5842,371,584
\\DB04\Process(svchost#2)\Private Bytes6,037,5046,037,5046,037,504006,037,5046,037,5046,037,504
\\DB04\Process(svchost#1)\Private Bytes2,228,2242,266,0132,277,37677,60819,5672,269,4992,274,5092,277,376
\\DB04\Process(svchost)\Private Bytes1,540,0961,580,7921,589,248-310,43418,0781,584,8371,589,2481,589,248
\\DB04\Process(lsass)\Private Bytes12,435,45612,508,47912,591,104459,18342,10212,509,09212,509,11612,514,962
\\DB04\Process(services)\Private Bytes6,664,1926,720,8426,762,496-594,99841,6626,724,1756,727,4246,732,581
\\DB04\Process(winlogon)\Private Bytes11,288,57611,313,94511,386,880-310,43436,00111,311,26211,304,14111,300,279
\\DB04\Process(csrss)\Private Bytes1,941,5041,941,5041,941,504001,941,5041,941,5041,941,504
\\DB04\Process(smss)\Private Bytes253,952253,952253,95200253,952253,952253,952
\\DB04\Process(System)\Private Bytes94,20894,20894,2080094,20894,20894,208
\\DB04\Process(Idle)\Private Bytes0-000---
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
*OK\\DB04\Process(dfrgifc)\Private Bytes1,515,5201,650,6881,732,608-
*OK\\DB04\Process(powershell#4)\Private Bytes52,613,12052,613,12052,613,120-
*OK\\DB04\Process(cmd#4)\Private Bytes1,978,3681,978,3681,978,368-
*OK\\DB04\Process(powershell#3)\Private Bytes50,417,66450,417,66450,417,664-
*OK\\DB04\Process(cmd#3)\Private Bytes1,978,3681,978,3681,978,368-
*OK\\DB04\Process(powershell#2)\Private Bytes51,720,19253,468,67855,861,24814,687,394
*OK\\DB04\Process(cmd#2)\Private Bytes1,978,3681,978,3681,978,3680
*OK\\DB04\Process(SQLCMD#1)\Private Bytes4,366,3364,366,3364,366,336-
*OK\\DB04\Process(SQLCMD)\Private Bytes4,878,3364,908,2964,935,680-232,825
*OK\\DB04\Process(msinfo32)\Private Bytes4,231,1687,749,7469,240,576262,154,779
*OK\\DB04\Process(cmd#1)\Private Bytes1,978,3682,157,5353,829,760-11,693,002
*OK\\DB04\Process(SQLdiag)\Private Bytes16,678,91216,891,47516,945,152866,627
*OK\\DB04\Process(powershell#1)\Private Bytes52,850,68852,867,53452,899,840-310,434
*OK\\DB04\Process(cmd)\Private Bytes1,974,2721,974,2721,974,2720
*OK\\DB04\Process(explorer#1)\Private Bytes7,897,0887,947,0338,044,544-931,301
*OK\\DB04\Process(svchost#8)\Private Bytes3,960,8323,960,8323,960,8320
*OK\\DB04\Process(SQLAGENT)\Private Bytes24,678,40024,813,17224,817,664879,562
*OK\\DB04\Process(fdhost)\Private Bytes5,095,4245,143,7835,144,5760
12/16/2009 1:06:41 PMMemory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,450,659,8401,481,544,7041,493,245,95256,387,368.4210526
12/16/2009 1:07:00 PMMemory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,492,819,9681,499,601,9201,508,446,208430,274,021.052632
12/16/2009 1:07:19 PMMemory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,508,077,5681,508,388,8641,508,675,584553,736,084.210526
12/16/2009 1:07:38 PMMemory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,508,528,1281,512,427,5201,514,430,464572,961,806.698565
12/16/2009 1:07:57 PMMemory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,514,323,9681,514,323,9681,514,323,968555,158,905.263158
12/16/2009 1:08:16 PMMemory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,514,323,9681,519,169,5361,533,706,240583,078,037.246964
12/16/2009 1:08:35 PMMemory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,538,629,6321,538,629,6321,538,629,632804,799,326.31579
12/16/2009 1:08:54 PMMemory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,538,629,6321,538,629,6321,538,629,632751,146,037.894737
12/16/2009 1:09:13 PMMemory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,538,629,6321,538,629,6321,538,629,632704,199,410.526316
12/16/2009 1:09:32 PMMemory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,538,629,6321,538,629,6321,538,629,632662,775,915.789474
12/16/2009 1:09:51 PMMemory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,538,629,6321,538,629,6321,538,629,632625,955,031.578947
12/16/2009 1:10:10 PMMemory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,538,629,6321,538,629,6321,538,629,632593,010,029.916898
12/16/2009 1:10:29 PMMemory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,538,695,1681,538,695,1681,538,695,168563,980,395.789474
12/16/2009 1:10:48 PMMemory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,538,695,1681,538,695,1681,538,695,168537,124,186.466165
12/16/2009 1:11:07 PMMemory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,538,695,1681,538,695,1681,538,695,168512,709,450.717703
12/16/2009 1:11:26 PMMemory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,538,695,1681,538,695,1681,538,695,168490,417,735.469108
12/16/2009 1:11:45 PMMemory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,538,695,1681,538,695,1681,538,695,168469,983,663.157895
12/16/2009 1:12:04 PMMemory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,538,695,1681,538,695,1681,538,695,168451,184,316.631579
12/16/2009 1:12:23 PMMemory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,538,695,1681,538,695,1681,538,695,168433,831,073.684211
12/16/2009 1:12:42 PMMemory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,538,695,1681,538,695,1681,538,695,168417,763,256.140351
12/16/2009 1:13:01 PMMemory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,538,695,1681,538,727,9361,538,826,240403,064,878.195489
12/16/2009 1:13:20 PMMemory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,532,592,1281,536,638,9761,538,695,168375,517,711.796733
12/16/2009 1:13:39 PMMemory: an increasing trend of 10MB's per hour detected\\DB04\Process(sqlservr)\Private Bytes1,520,164,8641,522,061,3121,523,957,760270,930,997.894737
Back to the top

Handle Leak Detection

Description: This analysis checks all of the processes to determine how many handles each has open and determines if a handle leaks is suspected. A process with a large number of handles and/or an aggresive upward trend could indicate a handle leak which typically results in a memory leak. The total number of handles currently open by this process. This number is equal to the sum of the handles currently open by each thread in this process.

\Process(*)\Handle Count

\Process(*)\Handle Count

\Process(*)\Handle Count

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\Process(_Total)\Handle Count12,91313,03913,638-2,4828313,03613,04013,051
\\DB04\Process(dfrgifc)\Handle Count7194106-0---
\\DB04\Process(powershell#4)\Handle Count216216216-0---
\\DB04\Process(cmd#4)\Handle Count353535-0---
\\DB04\Process(powershell#3)\Handle Count215215215-0---
\\DB04\Process(cmd#3)\Handle Count353535-0---
\\DB04\Process(powershell#2)\Handle Count217225229573226226225
\\DB04\Process(cmd#2)\Handle Count35353500353535
\\DB04\Process(SQLCMD#1)\Handle Count136136136-0---
\\DB04\Process(SQLCMD)\Handle Count133133137-251133133133
\\DB04\Process(msinfo32)\Handle Count989910063099100100
\\DB04\Process(cmd#1)\Handle Count3542109-46722383535
\\DB04\Process(SQLdiag)\Handle Count278278280-30278278278
\\DB04\Process(powershell#1)\Handle Count235237242-322237237237
\\DB04\Process(cmd)\Handle Count30303000303030
\\DB04\Process(explorer#1)\Handle Count270271273-191271271271
\\DB04\Process(svchost#8)\Handle Count22722722700227227227
\\DB04\Process(SQLAGENT)\Handle Count37037037000370370370
\\DB04\Process(fdhost)\Handle Count13613613600136136136
\\DB04\Process(sqlservr)\Handle Count64374578988957754766779
\\DB04\Process(Ssms)\Handle Count80280981623809809809
\\DB04\Process(wpabaln)\Handle Count41414100414141
\\DB04\Process(powershell)\Handle Count42142142100421421421
\\DB04\Process(wmiprvse#1)\Handle Count15915915900159159159
\\DB04\Process(explorer)\Handle Count42642943001429429429
\\DB04\Process(wmiprvse)\Handle Count1,4091,6911,709341171,6931,6931,695
\\DB04\Process(alg)\Handle Count88888800888888
\\DB04\Process(fdlauncher)\Handle Count37373700373737
\\DB04\Process(svchost#7)\Handle Count145149154-442149149149
\\DB04\Process(sqlwriter)\Handle Count83838300838383
\\DB04\Process(svchost#6)\Handle Count42424200424242
\\DB04\Process(MsDtsSrvr)\Handle Count16316316300163163163
\\DB04\Process(svchost#5)\Handle Count69696900696969
\\DB04\Process(msdtc)\Handle Count15315315300153153153
\\DB04\Process(vmicsvc#4)\Handle Count88888800888888
\\DB04\Process(vmicsvc#3)\Handle Count87878700878787
\\DB04\Process(vmicsvc#2)\Handle Count78787800787878
\\DB04\Process(vmicsvc#1)\Handle Count15415415400154154154
\\DB04\Process(vmicsvc)\Handle Count10210210200102102102
\\DB04\Process(spoolsv)\Handle Count123126127-241127127127
\\DB04\Process(svchost#4)\Handle Count1,2841,3491,374-325211,3551,3561,358
\\DB04\Process(svchost#3)\Handle Count188189192-251188188188
\\DB04\Process(svchost#2)\Handle Count150152155-91152152152
\\DB04\Process(svchost#1)\Handle Count256264277-985264264264
\\DB04\Process(svchost)\Handle Count899191-131919191
\\DB04\Process(lsass)\Handle Count702711741-2129710709708
\\DB04\Process(services)\Handle Count367370375-352370370370
\\DB04\Process(winlogon)\Handle Count685686692-442686686685
\\DB04\Process(csrss)\Handle Count633648688-1538648648648
\\DB04\Process(smss)\Handle Count19191900191919
\\DB04\Process(System)\Handle Count868877884555878879879
\\DB04\Process(Idle)\Handle Count0-000---
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
*OK\\DB04\Process(dfrgifc)\Handle Count7194106-
*OK\\DB04\Process(powershell#4)\Handle Count216216216-
*OK\\DB04\Process(cmd#4)\Handle Count353535-
*OK\\DB04\Process(powershell#3)\Handle Count215215215-
*OK\\DB04\Process(cmd#3)\Handle Count353535-
*OK\\DB04\Process(powershell#2)\Handle Count21722522957
*OK\\DB04\Process(cmd#2)\Handle Count3535350
*OK\\DB04\Process(SQLCMD#1)\Handle Count136136136-
*OK\\DB04\Process(SQLCMD)\Handle Count133133137-25
*OK\\DB04\Process(msinfo32)\Handle Count989910063
*OK\\DB04\Process(cmd#1)\Handle Count3542109-467
*OK\\DB04\Process(SQLdiag)\Handle Count278278280-3
*OK\\DB04\Process(powershell#1)\Handle Count235237242-32
*OK\\DB04\Process(cmd)\Handle Count3030300
*OK\\DB04\Process(explorer#1)\Handle Count270271273-19
*OK\\DB04\Process(svchost#8)\Handle Count2272272270
*OK\\DB04\Process(SQLAGENT)\Handle Count3703703700
*OK\\DB04\Process(fdhost)\Handle Count1361361360
*OK\\DB04\Process(sqlservr)\Handle Count643745789889
*OK\\DB04\Process(Ssms)\Handle Count8028098162
*OK\\DB04\Process(wpabaln)\Handle Count4141410
*OK\\DB04\Process(powershell)\Handle Count4214214210
*OK\\DB04\Process(wmiprvse#1)\Handle Count1591591590
*OK\\DB04\Process(explorer)\Handle Count4264294300
*OK\\DB04\Process(wmiprvse)\Handle Count1,4091,6911,709341
*OK\\DB04\Process(alg)\Handle Count8888880
*OK\\DB04\Process(fdlauncher)\Handle Count3737370
*OK\\DB04\Process(svchost#7)\Handle Count145149154-44
*OK\\DB04\Process(sqlwriter)\Handle Count8383830
*OK\\DB04\Process(svchost#6)\Handle Count4242420
*OK\\DB04\Process(MsDtsSrvr)\Handle Count1631631630
*OK\\DB04\Process(svchost#5)\Handle Count6969690
*OK\\DB04\Process(msdtc)\Handle Count1531531530
*OK\\DB04\Process(vmicsvc#4)\Handle Count8888880
*OK\\DB04\Process(vmicsvc#3)\Handle Count8787870
*OK\\DB04\Process(vmicsvc#2)\Handle Count7878780
*OK\\DB04\Process(vmicsvc#1)\Handle Count1541541540
*OK\\DB04\Process(vmicsvc)\Handle Count1021021020
*OK\\DB04\Process(spoolsv)\Handle Count123126127-24
*OK\\DB04\Process(svchost#4)\Handle Count1,2841,3491,374-325
*OK\\DB04\Process(svchost#3)\Handle Count188189192-25
*OK\\DB04\Process(svchost#2)\Handle Count150152155-9
*OK\\DB04\Process(svchost#1)\Handle Count256264277-98
*OK\\DB04\Process(svchost)\Handle Count899191-13
*OK\\DB04\Process(lsass)\Handle Count702711741-212
*OK\\DB04\Process(services)\Handle Count367370375-35
*OK\\DB04\Process(winlogon)\Handle Count685686692-44
*OK\\DB04\Process(csrss)\Handle Count633648688-153
*OK\\DB04\Process(smss)\Handle Count1919190
Back to the top

Process Thread Count

Description: The number of threads currently active in this process. An instruction is the basic unit of execution in a processor, and a thread is the object that executes instructions. Every running process has at least one thread.

This analysis checks all of the processes to determine if a process has more than 500 threads and if it is on an increasing trend of 50 threads per hour. A process with a large number of threads and/or an aggressive upward trend could indicate a thread leak which typically results in either a memory leak or high context switching. High context switching will result in high privileged mode CPU.

\Process(*)\Thread Count

\Process(*)\Thread Count

\Process(*)\Thread Count

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\Process(_Total)\Thread Count521535561-1047536535535
\\DB04\Process(dfrgifc)\Thread Count667-0---
\\DB04\Process(powershell#4)\Thread Count888-0---
\\DB04\Process(cmd#4)\Thread Count111-0---
\\DB04\Process(powershell#3)\Thread Count888-0---
\\DB04\Process(cmd#3)\Thread Count111-0---
\\DB04\Process(powershell#2)\Thread Count788-60888
\\DB04\Process(cmd#2)\Thread Count11100111
\\DB04\Process(SQLCMD#1)\Thread Count555-0---
\\DB04\Process(SQLCMD)\Thread Count345-131444
\\DB04\Process(msinfo32)\Thread Count66600666
\\DB04\Process(cmd#1)\Thread Count112-60111
\\DB04\Process(SQLdiag)\Thread Count455-60555
\\DB04\Process(powershell#1)\Thread Count678-131776
\\DB04\Process(cmd)\Thread Count11100111
\\DB04\Process(explorer#1)\Thread Count456-131555
\\DB04\Process(svchost#8)\Thread Count16161600161616
\\DB04\Process(SQLAGENT)\Thread Count14141400141414
\\DB04\Process(fdhost)\Thread Count56600666
\\DB04\Process(sqlservr)\Thread Count48718119712737578
\\DB04\Process(Ssms)\Thread Count19202020202020
\\DB04\Process(wpabaln)\Thread Count11100111
\\DB04\Process(powershell)\Thread Count77700777
\\DB04\Process(wmiprvse#1)\Thread Count44400444
\\DB04\Process(explorer)\Thread Count91010-60101010
\\DB04\Process(wmiprvse)\Thread Count161820-171181818
\\DB04\Process(alg)\Thread Count55500555
\\DB04\Process(fdlauncher)\Thread Count11100111
\\DB04\Process(svchost#7)\Thread Count151717-61171717
\\DB04\Process(sqlwriter)\Thread Count33300333
\\DB04\Process(svchost#6)\Thread Count22200222
\\DB04\Process(MsDtsSrvr)\Thread Count66600666
\\DB04\Process(svchost#5)\Thread Count22200222
\\DB04\Process(msdtc)\Thread Count13131300131313
\\DB04\Process(vmicsvc#4)\Thread Count33300333
\\DB04\Process(vmicsvc#3)\Thread Count33300333
\\DB04\Process(vmicsvc#2)\Thread Count33300333
\\DB04\Process(vmicsvc#1)\Thread Count55500555
\\DB04\Process(vmicsvc)\Thread Count33300333
\\DB04\Process(spoolsv)\Thread Count111313-131131313
\\DB04\Process(svchost#4)\Thread Count576167-553616060
\\DB04\Process(svchost#3)\Thread Count151516-60151515
\\DB04\Process(svchost#2)\Thread Count99900999
\\DB04\Process(svchost#1)\Thread Count10111120111111
\\DB04\Process(svchost)\Thread Count566-60666
\\DB04\Process(lsass)\Thread Count313233-61323232
\\DB04\Process(services)\Thread Count161718-131171717
\\DB04\Process(winlogon)\Thread Count181920-61181818
\\DB04\Process(csrss)\Thread Count15151500151515
\\DB04\Process(smss)\Thread Count33300333
\\DB04\Process(System)\Thread Count727273-20727272
\\DB04\Process(Idle)\Thread Count22200222
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
*OK\\DB04\Process(dfrgifc)\Thread Count667-
*OK\\DB04\Process(powershell#4)\Thread Count888-
*OK\\DB04\Process(cmd#4)\Thread Count111-
*OK\\DB04\Process(powershell#3)\Thread Count888-
*OK\\DB04\Process(cmd#3)\Thread Count111-
*OK\\DB04\Process(powershell#2)\Thread Count788-6
*OK\\DB04\Process(cmd#2)\Thread Count1110
*OK\\DB04\Process(SQLCMD#1)\Thread Count555-
*OK\\DB04\Process(SQLCMD)\Thread Count345-13
*OK\\DB04\Process(msinfo32)\Thread Count6660
*OK\\DB04\Process(cmd#1)\Thread Count112-6
*OK\\DB04\Process(SQLdiag)\Thread Count455-6
*OK\\DB04\Process(powershell#1)\Thread Count678-13
*OK\\DB04\Process(cmd)\Thread Count1110
*OK\\DB04\Process(explorer#1)\Thread Count456-13
*OK\\DB04\Process(svchost#8)\Thread Count1616160
*OK\\DB04\Process(SQLAGENT)\Thread Count1414140
*OK\\DB04\Process(fdhost)\Thread Count5660
*OK\\DB04\Process(sqlservr)\Thread Count487181197
*OK\\DB04\Process(Ssms)\Thread Count1920202
*OK\\DB04\Process(wpabaln)\Thread Count1110
*OK\\DB04\Process(powershell)\Thread Count7770
*OK\\DB04\Process(wmiprvse#1)\Thread Count4440
*OK\\DB04\Process(explorer)\Thread Count91010-6
*OK\\DB04\Process(wmiprvse)\Thread Count161820-17
*OK\\DB04\Process(alg)\Thread Count5550
*OK\\DB04\Process(fdlauncher)\Thread Count1110
*OK\\DB04\Process(svchost#7)\Thread Count151717-6
*OK\\DB04\Process(sqlwriter)\Thread Count3330
*OK\\DB04\Process(svchost#6)\Thread Count2220
*OK\\DB04\Process(MsDtsSrvr)\Thread Count6660
*OK\\DB04\Process(svchost#5)\Thread Count2220
*OK\\DB04\Process(msdtc)\Thread Count1313130
*OK\\DB04\Process(vmicsvc#4)\Thread Count3330
*OK\\DB04\Process(vmicsvc#3)\Thread Count3330
*OK\\DB04\Process(vmicsvc#2)\Thread Count3330
*OK\\DB04\Process(vmicsvc#1)\Thread Count5550
*OK\\DB04\Process(vmicsvc)\Thread Count3330
*OK\\DB04\Process(spoolsv)\Thread Count111313-13
*OK\\DB04\Process(svchost#4)\Thread Count576167-55
*OK\\DB04\Process(svchost#3)\Thread Count151516-6
*OK\\DB04\Process(svchost#2)\Thread Count9990
*OK\\DB04\Process(svchost#1)\Thread Count1011112
*OK\\DB04\Process(svchost)\Thread Count566-6
*OK\\DB04\Process(lsass)\Thread Count313233-6
*OK\\DB04\Process(services)\Thread Count161718-13
*OK\\DB04\Process(winlogon)\Thread Count181920-6
*OK\\DB04\Process(csrss)\Thread Count1515150
*OK\\DB04\Process(smss)\Thread Count3330
Back to the top

High Virtual Memory Usage

Description: This analysis determines if any of the processes are consuming a large of virtual memory. 32-bit processes by default are only allowed to access up to 2GB's of user mode memory. If the process becomes close to this maximum, then it could starve for memory. If a process is becoming close to it's maximum, then consider moving the process to a 64-bit system. The /3GB switch could be used to give the user mode process a total of 3GB's of addressable memory, but this takes away 1GB of memory from the kernel which could have worse affects on the entire system such as with Pool Paged Memory and Pool Non-Paged Memory.

\Process(*)\Virtual Bytes

\Process(*)\Virtual Bytes

\Process(*)\Virtual Bytes

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\Process(_Total)\Virtual Bytes14,033,108,99214,085,652,56815,321,989,120-2,616,354,49375,228,32614,074,463,35014,072,244,68514,070,588,587
\\DB04\Process(dfrgifc)\Virtual Bytes32,862,20834,293,07735,532,800-0---
\\DB04\Process(powershell#4)\Virtual Bytes555,057,152555,057,152555,057,152-0---
\\DB04\Process(cmd#4)\Virtual Bytes17,014,78417,014,78417,014,784-0---
\\DB04\Process(powershell#3)\Virtual Bytes556,105,728556,105,728556,105,728-0---
\\DB04\Process(cmd#3)\Virtual Bytes17,014,78417,014,78417,014,784-0---
\\DB04\Process(powershell#2)\Virtual Bytes556,105,728559,235,006565,084,16055,076,1092,745,289559,161,029558,910,669559,073,573
\\DB04\Process(cmd#2)\Virtual Bytes17,014,78417,014,78417,014,7840017,014,78417,014,78417,014,784
\\DB04\Process(SQLCMD#1)\Virtual Bytes67,067,90467,067,90467,067,904-0---
\\DB04\Process(SQLCMD)\Virtual Bytes67,067,90467,642,93069,165,056-13,245,171618,98467,602,27467,605,29967,610,917
\\DB04\Process(msinfo32)\Virtual Bytes59,789,31265,206,95566,080,768223,512,2531,055,83365,206,95565,949,69665,949,696
\\DB04\Process(cmd#1)\Virtual Bytes17,014,78419,718,93744,957,696-176,481,5498,261,32318,089,51117,014,78417,014,784
\\DB04\Process(SQLdiag)\Virtual Bytes93,011,96893,546,62894,068,736-6,609,651516,00193,568,39493,577,42193,594,185
\\DB04\Process(powershell#1)\Virtual Bytes553,938,944554,298,335554,987,520-6,622,585418,435554,286,789554,233,856554,182,363
\\DB04\Process(cmd)\Virtual Bytes17,018,88017,018,88017,018,8800017,018,88017,018,88017,018,880
\\DB04\Process(explorer#1)\Virtual Bytes109,105,152109,460,315110,153,728-6,622,585338,197109,447,956109,439,386109,470,281
\\DB04\Process(svchost#8)\Virtual Bytes51,781,63251,781,63251,781,6320051,781,63251,781,63251,781,632
\\DB04\Process(SQLAGENT)\Virtual Bytes531,070,976531,070,976531,070,97600531,070,976531,070,976531,070,976
\\DB04\Process(fdhost)\Virtual Bytes40,017,92040,533,75240,542,208032,20040,542,20840,542,20840,542,208
\\DB04\Process(sqlservr)\Virtual Bytes5,746,880,5125,795,491,4885,817,135,104421,775,89926,133,8095,799,449,4165,804,606,5325,811,010,219
\\DB04\Process(Ssms)\Virtual Bytes556,937,216557,772,271558,247,9362,069,558621,945557,832,034557,903,872558,037,285
\\DB04\Process(wpabaln)\Virtual Bytes55,492,60855,492,60855,492,6080055,492,60855,492,60855,492,608
\\DB04\Process(powershell)\Virtual Bytes605,962,240605,962,240605,962,24000605,962,240605,962,240605,962,240
\\DB04\Process(wmiprvse#1)\Virtual Bytes40,382,46440,382,46440,382,4640040,382,46440,382,46440,382,464
\\DB04\Process(explorer)\Virtual Bytes123,330,560123,630,757123,854,848-3,311,293256,142123,648,158123,664,794123,695,689
\\DB04\Process(wmiprvse)\Virtual Bytes155,283,456184,267,853196,575,232-49,908,68215,275,838186,396,094188,120,149191,421,928
\\DB04\Process(alg)\Virtual Bytes30,244,86430,244,86430,244,8640030,244,86430,244,86430,244,864
\\DB04\Process(fdlauncher)\Virtual Bytes20,078,59220,078,59220,078,5920020,078,59220,078,59220,078,592
\\DB04\Process(svchost#7)\Virtual Bytes72,953,85673,789,61674,002,432-3,311,293396,52873,869,68073,969,66474,002,432
\\DB04\Process(sqlwriter)\Virtual Bytes37,679,10437,679,10437,679,1040037,679,10437,679,10437,679,104
\\DB04\Process(svchost#6)\Virtual Bytes16,613,37616,613,37616,613,3760016,613,37616,613,37616,613,376
\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,456002,822,803,4562,822,803,4562,822,803,456
\\DB04\Process(svchost#5)\Virtual Bytes25,645,05625,645,05625,645,0560025,645,05625,645,05625,645,056
\\DB04\Process(msdtc)\Virtual Bytes38,940,67238,940,67238,940,6720038,940,67238,940,67238,940,672
\\DB04\Process(vmicsvc#4)\Virtual Bytes45,465,60045,465,60045,465,6000045,465,60045,465,60045,465,600
\\DB04\Process(vmicsvc#3)\Virtual Bytes42,557,44042,557,44042,557,4400042,557,44042,557,44042,557,440
\\DB04\Process(vmicsvc#2)\Virtual Bytes42,704,89642,704,89642,704,8960042,704,89642,704,89642,704,896
\\DB04\Process(vmicsvc#1)\Virtual Bytes77,250,56077,250,56077,250,5600077,250,56077,250,56077,250,560
\\DB04\Process(vmicsvc)\Virtual Bytes52,248,57652,248,57652,248,5760052,248,57652,248,57652,248,576
\\DB04\Process(spoolsv)\Virtual Bytes58,556,41658,990,50459,080,704-3,311,293192,83259,033,65359,080,70459,080,704
\\DB04\Process(svchost#4)\Virtual Bytes535,433,216558,153,453580,907,008-219,534,82121,029,278559,068,436559,508,326560,431,372
\\DB04\Process(svchost#3)\Virtual Bytes40,239,10440,268,70140,763,392-3,311,293113,92440,239,10440,239,10440,239,104
\\DB04\Process(svchost#2)\Virtual Bytes69,795,84069,795,84069,795,8400069,795,84069,795,84069,795,840
\\DB04\Process(svchost#1)\Virtual Bytes33,902,59234,305,67434,426,880827,823208,71134,342,85934,396,29734,426,880
\\DB04\Process(svchost)\Virtual Bytes29,597,69630,031,78430,121,984-3,311,293192,83230,074,93330,121,98430,121,984
\\DB04\Process(lsass)\Virtual Bytes75,223,04075,785,38176,271,616-3,311,293376,94475,812,86475,832,52575,803,502
\\DB04\Process(services)\Virtual Bytes318,431,232319,083,245319,545,344-5,794,762440,221319,115,369319,143,663319,188,407
\\DB04\Process(winlogon)\Virtual Bytes84,213,76084,484,36085,262,336-3,311,293384,01384,455,73984,379,78584,338,590
\\DB04\Process(csrss)\Virtual Bytes55,136,25655,153,16955,660,544-1,655,64655,12855,141,29755,136,25655,136,256
\\DB04\Process(smss)\Virtual Bytes5,218,3045,218,3045,218,304005,218,3045,218,3045,218,304
\\DB04\Process(System)\Virtual Bytes2,490,3682,490,3682,490,368002,490,3682,490,3682,490,368
\\DB04\Process(Idle)\Virtual Bytes0-000---
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
*OK\\DB04\Process(dfrgifc)\Virtual Bytes32,862,20834,293,07735,532,800-
*OK\\DB04\Process(powershell#4)\Virtual Bytes555,057,152555,057,152555,057,152-
*OK\\DB04\Process(cmd#4)\Virtual Bytes17,014,78417,014,78417,014,784-
*OK\\DB04\Process(powershell#3)\Virtual Bytes556,105,728556,105,728556,105,728-
*OK\\DB04\Process(cmd#3)\Virtual Bytes17,014,78417,014,78417,014,784-
*OK\\DB04\Process(powershell#2)\Virtual Bytes556,105,728559,235,006565,084,16055,076,109
*OK\\DB04\Process(cmd#2)\Virtual Bytes17,014,78417,014,78417,014,7840
*OK\\DB04\Process(SQLCMD#1)\Virtual Bytes67,067,90467,067,90467,067,904-
*OK\\DB04\Process(SQLCMD)\Virtual Bytes67,067,90467,642,93069,165,056-13,245,171
*OK\\DB04\Process(msinfo32)\Virtual Bytes59,789,31265,206,95566,080,768223,512,253
*OK\\DB04\Process(cmd#1)\Virtual Bytes17,014,78419,718,93744,957,696-176,481,549
*OK\\DB04\Process(SQLdiag)\Virtual Bytes93,011,96893,546,62894,068,736-6,609,651
*OK\\DB04\Process(powershell#1)\Virtual Bytes553,938,944554,298,335554,987,520-6,622,585
*OK\\DB04\Process(cmd)\Virtual Bytes17,018,88017,018,88017,018,8800
*OK\\DB04\Process(explorer#1)\Virtual Bytes109,105,152109,460,315110,153,728-6,622,585
*OK\\DB04\Process(svchost#8)\Virtual Bytes51,781,63251,781,63251,781,6320
*OK\\DB04\Process(SQLAGENT)\Virtual Bytes531,070,976531,070,976531,070,9760
*OK\\DB04\Process(fdhost)\Virtual Bytes40,017,92040,533,75240,542,2080
*OK\\DB04\Process(Ssms)\Virtual Bytes556,937,216557,772,271558,247,9362,069,558
*OK\\DB04\Process(wpabaln)\Virtual Bytes55,492,60855,492,60855,492,6080
*OK\\DB04\Process(powershell)\Virtual Bytes605,962,240605,962,240605,962,2400
*OK\\DB04\Process(wmiprvse#1)\Virtual Bytes40,382,46440,382,46440,382,4640
*OK\\DB04\Process(explorer)\Virtual Bytes123,330,560123,630,757123,854,848-3,311,293
*OK\\DB04\Process(wmiprvse)\Virtual Bytes155,283,456184,267,853196,575,232-49,908,682
*OK\\DB04\Process(alg)\Virtual Bytes30,244,86430,244,86430,244,8640
*OK\\DB04\Process(fdlauncher)\Virtual Bytes20,078,59220,078,59220,078,5920
*OK\\DB04\Process(svchost#7)\Virtual Bytes72,953,85673,789,61674,002,432-3,311,293
*OK\\DB04\Process(sqlwriter)\Virtual Bytes37,679,10437,679,10437,679,1040
*OK\\DB04\Process(svchost#6)\Virtual Bytes16,613,37616,613,37616,613,3760
12/16/2009 1:04:09 PMHigh User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
12/16/2009 1:04:28 PMHigh User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
12/16/2009 1:04:47 PMHigh User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
12/16/2009 1:05:06 PMHigh User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
12/16/2009 1:05:25 PMHigh User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
12/16/2009 1:05:44 PMHigh User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
12/16/2009 1:06:03 PMHigh User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
12/16/2009 1:06:22 PMHigh User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
12/16/2009 1:06:41 PMHigh User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
12/16/2009 1:07:00 PMHigh User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
12/16/2009 1:07:19 PMHigh User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
12/16/2009 1:07:38 PMHigh User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
12/16/2009 1:07:57 PMHigh User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
12/16/2009 1:08:16 PMHigh User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
12/16/2009 1:08:35 PMHigh User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
12/16/2009 1:08:54 PMHigh User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
12/16/2009 1:09:13 PMHigh User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
12/16/2009 1:09:32 PMHigh User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
12/16/2009 1:09:51 PMHigh User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
12/16/2009 1:10:10 PMHigh User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
12/16/2009 1:10:29 PMHigh User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
12/16/2009 1:10:48 PMHigh User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
12/16/2009 1:11:07 PMHigh User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
12/16/2009 1:11:26 PMHigh User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
12/16/2009 1:11:45 PMHigh User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
12/16/2009 1:12:04 PMHigh User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
12/16/2009 1:12:23 PMHigh User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
12/16/2009 1:12:42 PMHigh User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
12/16/2009 1:13:01 PMHigh User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
12/16/2009 1:13:20 PMHigh User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
12/16/2009 1:13:39 PMHigh User-mode Memory Usage - consuming more than 80% of available virtual memory\\DB04\Process(MsDtsSrvr)\Virtual Bytes2,822,803,4562,822,803,4562,822,803,4560
Back to the top

Process Working Set

Description: Working Set is the current size, in bytes, of the Working Set of this process. The Working Set is the set of memory pages touched recently by the threads in the process. If free memory in the computer is above a threshold, pages are left in the Working Set of a process even if they are not in use. When free memory falls below a threshold, pages are trimmed from Working Sets. If they are needed they will then be soft-faulted back into the Working Set before leaving main memory.
This analysis checks for an increasing trend of 10MB’s or more in each of the processes. Use in correlation with Available Memory Analysis.

References:

Detecting Memory Bottlenecks http://www.microsoft.com/resources/documentation/windowsnt/4/workstation/reskit/en-us/04memory.mspx?mfr=true

\Process(*)\Working Set

\Process(*)\Working Set

\Process(*)\Working Set

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\Process(_Total)\Working Set1,800,110,0801,828,314,3981,951,567,872-409,733,65918,355,7121,828,923,1431,831,158,3911,832,915,017
\\DB04\Process(dfrgifc)\Working Set4,153,3444,623,0194,857,856-0---
\\DB04\Process(powershell#4)\Working Set48,107,52048,107,52048,107,520-0---
\\DB04\Process(cmd#4)\Working Set2,277,3762,277,3762,277,376-0---
\\DB04\Process(powershell#3)\Working Set45,703,16845,703,16845,703,168-0---
\\DB04\Process(cmd#3)\Working Set2,273,2802,273,2802,273,280-0---
\\DB04\Process(powershell#2)\Working Set47,104,00049,984,33652,613,12023,528,2861,482,75550,090,10250,108,67250,115,511
\\DB04\Process(cmd#2)\Working Set2,281,4722,281,4722,281,472002,281,4722,281,4722,281,472
\\DB04\Process(SQLCMD#1)\Working Set9,633,7929,633,7929,633,792-0---
\\DB04\Process(SQLCMD)\Working Set10,170,36810,218,43010,235,904116,41313,86610,220,15010,221,26110,223,616
\\DB04\Process(msinfo32)\Working Set8,048,64011,620,35213,139,968267,264,0001,198,71211,620,35212,443,13612,443,136
\\DB04\Process(cmd#1)\Working Set2,281,4722,634,6535,931,008-23,049,7011,078,9852,421,8392,281,4722,281,472
\\DB04\Process(SQLdiag)\Working Set22,011,90422,272,88122,339,5841,047,71455,09322,276,37222,275,20922,272,878
\\DB04\Process(powershell#1)\Working Set47,366,14447,376,48347,394,816-129,3478,77647,376,46347,375,25847,373,897
\\DB04\Process(cmd)\Working Set2,478,0802,478,0802,478,080002,478,0802,478,0802,478,080
\\DB04\Process(explorer#1)\Working Set17,530,88017,543,30017,580,032-232,82513,50417,541,90817,541,32517,542,290
\\DB04\Process(svchost#8)\Working Set1,703,9361,703,9361,703,936001,703,9361,703,9361,703,936
\\DB04\Process(SQLAGENT)\Working Set8,118,2728,245,1168,249,344827,82323,1588,249,3448,249,3448,249,344
\\DB04\Process(fdhost)\Working Set1,073,1521,089,2721,089,53601,0061,089,5361,089,5361,089,536
\\DB04\Process(sqlservr)\Working Set1,335,029,7601,360,767,4941,375,408,128-114,013,23816,513,6181,362,614,1801,364,780,8681,367,059,212
\\DB04\Process(Ssms)\Working Set136,318,976136,401,458136,445,952666,13950,219136,407,552136,415,078136,422,254
\\DB04\Process(wpabaln)\Working Set413,696413,696413,69600413,696413,696413,696
\\DB04\Process(powershell)\Working Set25,821,18425,821,18425,821,1840025,821,18425,821,18425,821,184
\\DB04\Process(wmiprvse#1)\Working Set806,912806,912806,91200806,912806,912806,912
\\DB04\Process(explorer)\Working Set11,694,08011,703,46111,710,464-103,4788,00411,704,00511,704,52511,705,490
\\DB04\Process(wmiprvse)\Working Set45,064,19255,399,58958,576,896-17,157,9281,808,14755,674,64455,865,13956,214,065
\\DB04\Process(alg)\Working Set466,944466,944466,94400466,944466,944466,944
\\DB04\Process(fdlauncher)\Working Set397,312397,312397,31200397,312397,312397,312
\\DB04\Process(svchost#7)\Working Set2,613,2482,642,7132,650,112-129,34713,8972,645,5432,649,0882,650,112
\\DB04\Process(sqlwriter)\Working Set569,344569,344569,34400569,344569,344569,344
\\DB04\Process(svchost#6)\Working Set380,928380,928380,92800380,928380,928380,928
\\DB04\Process(MsDtsSrvr)\Working Set3,452,9283,452,9283,452,928003,452,9283,452,9283,452,928
\\DB04\Process(svchost#5)\Working Set307,200307,200307,20000307,200307,200307,200
\\DB04\Process(msdtc)\Working Set577,536577,536577,53600577,536577,536577,536
\\DB04\Process(vmicsvc#4)\Working Set577,536577,536577,53600577,536577,536577,536
\\DB04\Process(vmicsvc#3)\Working Set733,184733,184733,18400733,184733,184733,184
\\DB04\Process(vmicsvc#2)\Working Set495,616495,616495,61600495,616495,616495,616
\\DB04\Process(vmicsvc#1)\Working Set716,800716,800716,80000716,800716,800716,800
\\DB04\Process(vmicsvc)\Working Set872,448872,448872,44800872,448872,448872,448
\\DB04\Process(spoolsv)\Working Set1,839,1041,872,8851,880,064-232,82515,0211,876,2311,879,8591,880,064
\\DB04\Process(svchost#4)\Working Set23,797,76024,899,46329,315,072-9,739,857797,71724,915,36424,920,25224,922,673
\\DB04\Process(svchost#3)\Working Set1,892,3521,893,2771,908,736-103,4783,5601,892,3521,892,3521,892,352
\\DB04\Process(svchost#2)\Working Set2,138,1122,140,9312,146,30451,7393,8292,140,8432,140,4332,139,672
\\DB04\Process(svchost#1)\Working Set2,330,6242,345,7312,355,200-12,9358,4712,346,7452,347,8952,347,301
\\DB04\Process(svchost)\Working Set1,650,6881,671,0361,675,264-155,2179,0391,673,0581,675,2641,675,264
\\DB04\Process(lsass)\Working Set8,269,8248,383,5438,417,280743,74728,2468,388,5428,387,9088,388,852
\\DB04\Process(services)\Working Set4,775,9365,313,1845,857,280-1,416,354264,5445,290,0505,228,0155,180,709
\\DB04\Process(winlogon)\Working Set6,717,4406,725,8966,750,208-103,47812,0006,725,0026,722,6286,721,341
\\DB04\Process(csrss)\Working Set3,198,9763,202,1473,297,280-310,43410,3373,199,9213,198,9763,198,976
\\DB04\Process(smss)\Working Set204,800204,800204,80000204,800204,800204,800
\\DB04\Process(System)\Working Set258,048258,048258,04800258,048258,048258,048
\\DB04\Process(Idle)\Working Set24,57624,57624,5760024,57624,57624,576
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
*OK\\DB04\Process(_Total)\Working Set1,800,110,0801,828,314,3981,951,567,872-409,733,659
*OK\\DB04\Process(dfrgifc)\Working Set4,153,3444,623,0194,857,856-
*OK\\DB04\Process(powershell#4)\Working Set48,107,52048,107,52048,107,520-
*OK\\DB04\Process(cmd#4)\Working Set2,277,3762,277,3762,277,376-
*OK\\DB04\Process(powershell#3)\Working Set45,703,16845,703,16845,703,168-
*OK\\DB04\Process(cmd#3)\Working Set2,273,2802,273,2802,273,280-
*OK\\DB04\Process(powershell#2)\Working Set47,104,00049,984,33652,613,12023,528,286
*OK\\DB04\Process(cmd#2)\Working Set2,281,4722,281,4722,281,4720
*OK\\DB04\Process(SQLCMD#1)\Working Set9,633,7929,633,7929,633,792-
*OK\\DB04\Process(SQLCMD)\Working Set10,170,36810,218,43010,235,904116,413
*OK\\DB04\Process(msinfo32)\Working Set8,048,64011,620,35213,139,968267,264,000
*OK\\DB04\Process(cmd#1)\Working Set2,281,4722,634,6535,931,008-23,049,701
*OK\\DB04\Process(SQLdiag)\Working Set22,011,90422,272,88122,339,5841,047,714
*OK\\DB04\Process(powershell#1)\Working Set47,366,14447,376,48347,394,816-129,347
*OK\\DB04\Process(cmd)\Working Set2,478,0802,478,0802,478,0800
*OK\\DB04\Process(explorer#1)\Working Set17,530,88017,543,30017,580,032-232,825
*OK\\DB04\Process(svchost#8)\Working Set1,703,9361,703,9361,703,9360
*OK\\DB04\Process(SQLAGENT)\Working Set8,118,2728,245,1168,249,344827,823
*OK\\DB04\Process(fdhost)\Working Set1,073,1521,089,2721,089,5360
*OK\\DB04\Process(sqlservr)\Working Set1,335,029,7601,360,767,4941,375,408,128-114,013,238
*OK\\DB04\Process(Ssms)\Working Set136,318,976136,401,458136,445,952666,139
*OK\\DB04\Process(wpabaln)\Working Set413,696413,696413,6960
*OK\\DB04\Process(powershell)\Working Set25,821,18425,821,18425,821,1840
*OK\\DB04\Process(wmiprvse#1)\Working Set806,912806,912806,9120
*OK\\DB04\Process(explorer)\Working Set11,694,08011,703,46111,710,464-103,478
*OK\\DB04\Process(wmiprvse)\Working Set45,064,19255,399,58958,576,896-17,157,928
*OK\\DB04\Process(alg)\Working Set466,944466,944466,9440
*OK\\DB04\Process(fdlauncher)\Working Set397,312397,312397,3120
*OK\\DB04\Process(svchost#7)\Working Set2,613,2482,642,7132,650,112-129,347
*OK\\DB04\Process(sqlwriter)\Working Set569,344569,344569,3440
*OK\\DB04\Process(svchost#6)\Working Set380,928380,928380,9280
*OK\\DB04\Process(MsDtsSrvr)\Working Set3,452,9283,452,9283,452,9280
*OK\\DB04\Process(svchost#5)\Working Set307,200307,200307,2000
*OK\\DB04\Process(msdtc)\Working Set577,536577,536577,5360
*OK\\DB04\Process(vmicsvc#4)\Working Set577,536577,536577,5360
*OK\\DB04\Process(vmicsvc#3)\Working Set733,184733,184733,1840
*OK\\DB04\Process(vmicsvc#2)\Working Set495,616495,616495,6160
*OK\\DB04\Process(vmicsvc#1)\Working Set716,800716,800716,8000
*OK\\DB04\Process(vmicsvc)\Working Set872,448872,448872,4480
*OK\\DB04\Process(spoolsv)\Working Set1,839,1041,872,8851,880,064-232,825
*OK\\DB04\Process(svchost#4)\Working Set23,797,76024,899,46329,315,072-9,739,857
*OK\\DB04\Process(svchost#3)\Working Set1,892,3521,893,2771,908,736-103,478
*OK\\DB04\Process(svchost#2)\Working Set2,138,1122,140,9312,146,30451,739
*OK\\DB04\Process(svchost#1)\Working Set2,330,6242,345,7312,355,200-12,935
*OK\\DB04\Process(svchost)\Working Set1,650,6881,671,0361,675,264-155,217
*OK\\DB04\Process(lsass)\Working Set8,269,8248,383,5438,417,280743,747
*OK\\DB04\Process(services)\Working Set4,775,9365,313,1845,857,280-1,416,354
*OK\\DB04\Process(winlogon)\Working Set6,717,4406,725,8966,750,208-103,478
*OK\\DB04\Process(csrss)\Working Set3,198,9763,202,1473,297,280-310,434
*OK\\DB04\Process(smss)\Working Set204,800204,800204,8000
*OK\\DB04\Process(System)\Working Set258,048258,048258,0480
*OK\\DB04\Process(Idle)\Working Set24,57624,57624,5760
Back to the top

Memory System Cache Resident Bytes

Description: System Cache Resident Bytes is the size, in bytes, of the pageable operating system code in the file system cache. This value includes only current physical pages and does not include any virtual memory pages not currently resident. It does equal the System Cache value shown in Task Manager. As a result, this value may be smaller than the actual amount of virtual memory in use by the file system cache. This value is a component of Memory\\System Code Resident Bytes which represents all pageable operating system code that is currently in physical memory. This counter displays the last observed value only; it is not an average.

This analysis checks for an increasing trend of 10MB’s per hour. Under load, a server might use the System Cache in order to cache I/O activity such as disk. Use in correlation with Process IO Data Operations/sec and Process IO Other Operations/sec Analyses.

References:
File Cache Performance and Tuning http://technet.microsoft.com/en-us/library/bb742613.aspx

\Memory\System Cache Resident Bytes

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\Memory\System Cache Resident Bytes26,169,34426,655,41427,475,968-549,726288,78126,640,80426,616,09826,608,713
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
12/16/2009 1:05:06 PMIncreasing trend of more than 10MB's per hour detected\\DB04\Memory\System Cache Resident Bytes26,796,03226,846,20826,943,48821,212,968.4210526
12/16/2009 1:05:25 PMIncreasing trend of more than 10MB's per hour detected\\DB04\Memory\System Cache Resident Bytes26,357,76026,733,56826,865,66410,574,147.3684211
12/16/2009 1:07:19 PMIncreasing trend of more than 10MB's per hour detected\\DB04\Memory\System Cache Resident Bytes27,045,88827,096,06427,156,48011,098,004.2105263
12/16/2009 1:07:38 PMIncreasing trend of more than 10MB's per hour detected\\DB04\Memory\System Cache Resident Bytes27,172,86427,215,18927,254,78412,141,014.354067
12/16/2009 1:07:57 PMIncreasing trend of more than 10MB's per hour detected\\DB04\Memory\System Cache Resident Bytes27,271,16827,334,65627,394,04813,015,578.9473684
12/16/2009 1:08:16 PMIncreasing trend of more than 10MB's per hour detected\\DB04\Memory\System Cache Resident Bytes27,426,81627,453,44027,475,96813,745,645.3441296
Back to the top

Memory Pages Input/sec

Description: Pages Input/sec is the rate at which pages are read from disk to resolve hard page faults. Hard page faults occur when a process refers to a page in virtual memory that is not in its working set or elsewhere in physical memory, and must be retrieved from disk. When a page is faulted, the system tries to read multiple contiguous pages into memory to maximize the benefit of the read operation. Compare the value of Memory\\Pages Input/sec to the value of Memory\\Page Reads/sec to determine the average number of pages read into memory during each read operation.

Reference:
How to determine the appropriate page file size for 64-bit versions of Windows Server 2003 or Windows XP
http://support.microsoft.com/kb/889654


\Memory\Pages Input/sec

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\Memory\Pages Input/sec013259-1,20442200
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
12/16/2009 1:04:09 PMMore then 10 page file reads per second\\DB04\Memory\Pages Input/sec1161912440
12/16/2009 1:04:28 PMMore then 10 page file reads per second\\DB04\Memory\Pages Input/sec35149259-7,949
12/16/2009 1:04:47 PMMore then 10 page file reads per second\\DB04\Memory\Pages Input/sec0926-17,168
12/16/2009 1:05:06 PMMore then 10 page file reads per second\\DB04\Memory\Pages Input/sec033132-9,930
Back to the top

Memory Percent Committed Bytes In Use

Description: % Committed Bytes In Use is the ratio of Memory\\Committed Bytes to the Memory\\Commit Limit. Committed memory is the physical memory in use for which space has been reserved in the paging file should it need to be written to disk. The commit limit is determined by the size of the paging file. If the paging file is enlarged, the commit limit increases, and the ratio is reduced). This counter displays the current percentage value only; it is not an average.

This analysis checks if the amount of Commited memory is becoming close to the Commit Limit (RAM plus total page file sizes), If so, then identify if you have a memory leak. If no memory leak is identified, then consider adding more physical RAM or increase the size of your page files.

\Memory\% Committed Bytes In Use

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\Memory\% Committed Bytes In Use535557-11555555
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
*OK\\DB04\Memory\% Committed Bytes In Use535557-1
Back to the top

SQL Server Process


Process % Privileged Time

Description: % Privileged Time is the percentage of elapsed time that the process threads spent executing code in privileged mode. When a Windows system service is called, the service will often run in privileged mode to gain access to system-private data. Such data is protected from access by threads executing in user mode. Calls to the system can be explicit or implicit, such as page faults or interrupts. Unlike some early operating systems, Windows uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes. Some work done by Windows on behalf of the application might appear in other subsystem processes in addition to the privileged time in the process.

\Process(sqlservr)\% Privileged Time

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\Process(sqlservr)\% Privileged Time01491111
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
*OK\\DB04\Process(sqlservr)\% Privileged Time0149
Back to the top

SQLServer:Access Methods


SQLServer:Access Methods Forwarded Records/sec

Description: Rows with varchar columns can experience expansion when varchar values are updated with a longer string. In the case where the row cannot fit in the existing page, the row migrates and access to the row will traverse a pointer. This only happens on heaps (tables without clustered indexes). Recommendations include: Evaluate clustered index for heap tables. Consider using default values or char instead of varchar. In cases where clustered indexes cannot be used, drop non-clustered indexes, build a clustered index to reorg pages and rows, drop the clustered index, then recreate non-clustered indexes.

\SQLServer:Access Methods\Forwarded Records/sec

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\SQLServer:Access Methods\Forwarded Records/sec0-000---
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
*OK\\DB04\SQLServer:Access Methods\Forwarded Records/sec0-00
Back to the top

SQLServer:Access Methods FreeSpace Scans/sec

Description: Inserts into heaps will require SQL Server to perform freespace scans to identify pages with free space to insert rows. Freespace scans are additional I/O expense for inserts and can possibly cause contention on the GAM, SGAM, and PFS pages when many spids are inserting. Evaluate clustered index for base tables.

\SQLServer:Access Methods\FreeSpace Scans/sec

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\SQLServer:Access Methods\FreeSpace Scans/sec09742-1,56144000
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
12/16/2009 1:04:09 PM> 10% of the number of Batch Requests/Sec\\DB04\SQLServer:Access Methods\FreeSpace Scans/sec02477420
12/16/2009 1:04:47 PM> 10% of the number of Batch Requests/Sec\\DB04\SQLServer:Access Methods\FreeSpace Scans/sec041115-19,511
Back to the top

SQLServer:Access Methods Full Scans/sec

Description: This counter monitors the number of full scans on base tables or indexes. Values greater than 1 or 2 indicate that we are having table / Index page scans. If we see high CPU then we need to investigate this counter, otherwise if the full scans are on small tables we can ignore this counter. A few of the main causes of high Full Scans/sec are • Missing indexes • Too many rows requested Queries with missing indexes or too many rows requested will have a large number of logical reads and an increased CPU time.

\SQLServer:Access Methods\Full Scans/sec

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\SQLServer:Access Methods\Full Scans/sec0522994444
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
12/16/2009 1:04:28 PMRatio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec123221
12/16/2009 1:04:47 PMRatio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec248314
12/16/2009 1:05:06 PMRatio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec011-22
12/16/2009 1:05:25 PMRatio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec011-19
12/16/2009 1:05:44 PMRatio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec011-15
12/16/2009 1:06:03 PMRatio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec011-11
12/16/2009 1:06:22 PMRatio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec001-18
12/16/2009 1:06:41 PMRatio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec41521319
12/16/2009 1:07:00 PMRatio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec121519293
12/16/2009 1:07:19 PMRatio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec121518271
12/16/2009 1:07:38 PMRatio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec7913142
12/16/2009 1:07:57 PMRatio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec04848
12/16/2009 1:08:16 PMRatio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec02621
12/16/2009 1:08:35 PMRatio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec14843
12/16/2009 1:08:54 PMRatio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec04839
12/16/2009 1:09:13 PMRatio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec03921
12/16/2009 1:09:32 PMRatio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec04835
12/16/2009 1:09:51 PMRatio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec13723
12/16/2009 1:10:10 PMRatio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec03924
12/16/2009 1:10:29 PMRatio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec06842
12/16/2009 1:10:48 PMRatio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec02812
12/16/2009 1:11:07 PMRatio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec14727
12/16/2009 1:11:26 PMRatio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec04926
12/16/2009 1:11:45 PMRatio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec02611
12/16/2009 1:12:04 PMRatio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec15832
12/16/2009 1:12:23 PMRatio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec02810
12/16/2009 1:12:42 PMRatio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec04922
12/16/2009 1:13:01 PMRatio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec14822
12/16/2009 1:13:20 PMRatio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec13713
12/16/2009 1:13:39 PMRatio of Index searches/sec to Full scan/sec < 1000 to 1.\\DB04\SQLServer:Access Methods\Full Scans/sec12172299
Back to the top

SQLServer:Access Methods Page Splits/sec

Description: Number of page splits per second that occur as the result of overflowing index pages. Dependent upon table/index design. This value needs to be low as possible. Heavily fragmented indexes may be the result of high page splits/sec Recommendation: If the number of page splits is high, consider increasing the fillfactor of your indexes. An increased fillfactor helps to reduce page splits by increasing the amount of free space on each page. Note: This counter also includes new page allocations, and doesn’t mean there is an issue.

\SQLServer:Access Methods\Page Splits/sec

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\SQLServer:Access Methods\Page Splits/sec014-60111
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
*OK\\DB04\SQLServer:Access Methods\Page Splits/sec014-6
Back to the top

SQLServer:Access Methods Scan Point Revalidations/sec

Description: Number of times per second that the scan point had to be revalidated to continue the scan. If a page latch has to be released, due to contention, the scan point must be revalidated when the scan resumes. This can indicate hot spots in the data. Correlate this data with the range scans/sec counter. The higher the number of range scans on the same pages, the higher the number of scan point revalidations.

\SQLServer:Access Methods\Scan Point Revalidations/sec

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\SQLServer:Access Methods\Scan Point Revalidations/sec00100000
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
*OK\\DB04\SQLServer:Access Methods\Scan Point Revalidations/sec0010
Back to the top

SQLServer:Access Methods Workfiles Created/sec

Description: Number of workfiles created in the last second. Tempdb workfiles are used in processing hash operations when the amount of data being processed is too big to fit into the available memory. Recommendations: Make queries more efficient by adding/changing indexes, adding additional memory, etc.

\SQLServer:Access Methods\Workfiles Created/sec

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\SQLServer:Access Methods\Workfiles Created/sec0232-22111
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
12/16/2009 1:04:28 PMMore than 20 Workfiles created per second for every 100 Batch Requests \\DB04\SQLServer:Access Methods\Workfiles Created/sec513322,346
Back to the top

SQLServer:Access Methods Worktables Created/sec

Description: Number of worktables created in the last second. Tempdb workfiles are used in processing hash operations when the amount of data being processed is too big to fit into the available memory. You may be able to reduce this number by making the queries more efficient by adding/changing indexes, adding additional memory, etc.

\SQLServer:Access Methods\Worktables Created/sec

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\SQLServer:Access Methods\Worktables Created/sec0314553322
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
*OK\\DB04\SQLServer:Access Methods\Worktables Created/sec031455
Back to the top

SQLServer:Access Methods Index Searches/sec

Description: Number of index searches. Index searches are used to start range scans, single index record fetches, and to reposition within an index. Index searches are preferable to index and table scans. For OLTP applications, optimize for more index searches and less scans (preferably, 1 full scan for every 1000 index searches). Index and table scans are expensive I/O operations.

\SQLServer:Access Methods\Index Searches/sec

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\SQLServer:Access Methods\Index Searches/sec02372,923-5,794350168149150
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
*OK\\DB04\SQLServer:Access Methods\Index Searches/sec02372,923-5,794
Back to the top

SQLServer:Buffer Manager


SQLServer:Buffer Manager Buffer cache hit ratio

Description: This counter indicates how often SQL Server goes to the buffer, not the hard disk, to get data. The higher this ratio, the less often SQL Server has to go to the hard disk to fetch data, and performance overall is boosted. Unlike many of the other counters available for monitoring SQL Server, this counter averages the Buffer Cache Hit Ratio from the time the last instance of SQL Server was restarted. In other words, this counter is not a real-time measurement, but an average of all the days since SQL Server was last restarted. In OLTP applications, this ratio should exceed 90-95%. If it doesn't, then you need to add more RAM to your server to increase performance. In OLAP applications, the ratio could be much less because of the nature of how OLAP works. In any case, more RAM should increase the performance of SQL Server OLAP activity.

\SQLServer:Buffer Manager\Buffer cache hit ratio

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\SQLServer:Buffer Manager\Buffer cache hit ratio97100100-110100100100
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
*OK\\DB04\SQLServer:Buffer Manager\Buffer cache hit ratio97100100-11
Back to the top

SQLServer:Buffer Manager Free pages

Description: Total number of pages on all free lists.

\SQLServer:Buffer Manager\Free pages

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\SQLServer:Buffer Manager\Free pages252,35512,795-62,1133,4402,0191,523625
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
12/16/2009 1:07:00 PMFree Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages366301,229-197,626
12/16/2009 1:07:19 PMFree Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages165286417-184,372
12/16/2009 1:07:38 PMFree Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages139186250-169,332
12/16/2009 1:07:57 PMFree Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages104121127-156,257
12/16/2009 1:08:16 PMFree Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages111157251-143,705
12/16/2009 1:08:35 PMFree Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages25154241-133,488
12/16/2009 1:08:54 PMFree Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages180204237-123,954
12/16/2009 1:09:13 PMFree Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages140209306-116,143
12/16/2009 1:09:32 PMFree Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages147185238-109,580
12/16/2009 1:09:51 PMFree Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages123208385-103,253
12/16/2009 1:10:10 PMFree Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages128177248-98,125
12/16/2009 1:10:29 PMFree Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages90180268-93,196
12/16/2009 1:10:48 PMFree Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages144188231-88,687
12/16/2009 1:11:07 PMFree Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages160215372-84,421
12/16/2009 1:11:26 PMFree Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages115169255-81,130
12/16/2009 1:11:45 PMFree Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages72134203-78,022
12/16/2009 1:12:04 PMFree Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages163208255-74,339
12/16/2009 1:12:23 PMFree Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages128166184-71,790
12/16/2009 1:12:42 PMFree Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages101227379-68,704
12/16/2009 1:13:01 PMFree Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages92178231-66,581
12/16/2009 1:13:20 PMFree Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages66198400-64,155
12/16/2009 1:13:39 PMFree Pages < 640\\DB04\SQLServer:Buffer Manager\Free pages148182217-62,113
Back to the top

SQLServer:Buffer Manager Lazy writes/sec

Description: Number of buffers written by buffer manager's lazy writer. This counter tracks how many times a second that the Lazy Writer process is moving dirty pages from the buffer to disk in order to free up buffer space. Generally speaking, this should not be a high value, say more than 20 per second or so. Ideally, it should be close to zero. If it is zero, this indicates that your SQL Server's buffer cache is plenty big and SQL Server doesn't have to free up dirty pages, instead waiting for this to occur during regular checkpoints. If this value is high, then a need for more memory is indicated.

\SQLServer:Buffer Manager\Lazy writes/sec

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\SQLServer:Buffer Manager\Lazy writes/sec026588000
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
12/16/2009 1:10:10 PMLazy Writes/second > 20\\DB04\SQLServer:Buffer Manager\Lazy writes/sec324356426
12/16/2009 1:10:29 PMLazy Writes/second > 20\\DB04\SQLServer:Buffer Manager\Lazy writes/sec02265205
Back to the top

SQLServer:Buffer Manager Page life expectancy

Description: Number of seconds a page will stay in the buffer pool without references. This performance monitor counter tells you, on average, how long data pages are staying in the buffer. If this value gets below 300 seconds, this is a potential indication that your SQL Server could use more memory in order to boost performance.

\SQLServer:Buffer Manager\Page life expectancy

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\SQLServer:Buffer Manager\Page life expectancy189822115659958676
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
12/16/2009 1:04:09 PMPage Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy1826340
12/16/2009 1:04:28 PMPage Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy3947553,932
12/16/2009 1:04:47 PMPage Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy6065703,671
12/16/2009 1:05:06 PMPage Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy7582903,553
12/16/2009 1:05:25 PMPage Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy951021103,612
12/16/2009 1:05:44 PMPage Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy1151231303,657
12/16/2009 1:06:03 PMPage Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy1351431513,687
12/16/2009 1:06:22 PMPage Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy1561611663,647
12/16/2009 1:06:41 PMPage Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy1711781863,594
12/16/2009 1:07:00 PMPage Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy1911982063,621
12/16/2009 1:07:19 PMPage Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy2102172213,614
12/16/2009 1:07:38 PMPage Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy2212212213,355
12/16/2009 1:07:57 PMPage Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy2212212213,075
12/16/2009 1:08:16 PMPage Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy591802212,248
12/16/2009 1:08:35 PMPage Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy595959443
12/16/2009 1:08:54 PMPage Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy595959414
12/16/2009 1:09:13 PMPage Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy444444210
12/16/2009 1:09:32 PMPage Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy444444198
12/16/2009 1:09:51 PMPage Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy444650208
12/16/2009 1:10:10 PMPage Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy566471371
12/16/2009 1:10:29 PMPage Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy767980497
12/16/2009 1:10:48 PMPage Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy808080485
12/16/2009 1:11:07 PMPage Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy808080463
12/16/2009 1:11:26 PMPage Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy647680410
12/16/2009 1:11:45 PMPage Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy646464298
12/16/2009 1:12:04 PMPage Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy646464286
12/16/2009 1:12:23 PMPage Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy646464275
12/16/2009 1:12:42 PMPage Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy626264254
12/16/2009 1:13:01 PMPage Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy626262242
12/16/2009 1:13:20 PMPage Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy626262234
12/16/2009 1:13:39 PMPage Life Expectancy < 300 seconds\\DB04\SQLServer:Buffer Manager\Page life expectancy515151156
Back to the top

SQLServer:Buffer Manager Page lookups/sec

Description: Number of requests to find a page in the buffer pool. Number of requests to find a page in the buffer pool. When the ratio of page lookups to batch requests is greater than 100, this is an indication that while query plans are looking up data in the buffer pool, these plans are inefficient. Identify queries with the highest amount of logical I/O's and tune them.

\SQLServer:Buffer Manager\Page lookups/sec

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\SQLServer:Buffer Manager\Page lookups/sec018,401139,019493,88732,23814,1836,4422,641
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
12/16/2009 1:04:09 PMRatio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec39512,66132,6970
12/16/2009 1:04:28 PMRatio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec16,54634,53850,1244,145,035
12/16/2009 1:04:47 PMRatio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec23,63137,23144,6662,327,696
12/16/2009 1:05:06 PMRatio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec0197494-787,200
12/16/2009 1:05:25 PMRatio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec0149294-592,692
12/16/2009 1:06:03 PMRatio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec0166347-394,597
12/16/2009 1:06:22 PMRatio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2105281-339,882
12/16/2009 1:06:41 PMRatio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec8,96691,029139,0191,856,080
12/16/2009 1:07:00 PMRatio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec80,318101,723115,1691,874,984
12/16/2009 1:07:19 PMRatio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec88,46099,527107,9601,645,870
12/16/2009 1:07:38 PMRatio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec8,16555,304105,712734,517
12/16/2009 1:07:57 PMRatio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2,0692,6183,159-158,583
12/16/2009 1:08:16 PMRatio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2,1502,4272,809-149,170
12/16/2009 1:08:35 PMRatio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2,1282,5873,082-136,340
12/16/2009 1:08:54 PMRatio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2,2162,6733,177-126,162
12/16/2009 1:09:13 PMRatio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2,1172,3702,707-121,876
12/16/2009 1:09:32 PMRatio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2,3672,6572,974-111,499
12/16/2009 1:09:51 PMRatio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2,3522,5592,953-106,338
12/16/2009 1:10:10 PMRatio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2,1242,5903,059-100,439
12/16/2009 1:10:29 PMRatio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec1,7122,5693,373-95,613
12/16/2009 1:10:48 PMRatio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2,3532,6202,917-90,600
12/16/2009 1:11:07 PMRatio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2,5252,7303,024-85,533
12/16/2009 1:11:26 PMRatio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2,1262,4893,168-83,802
12/16/2009 1:11:45 PMRatio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2,2942,5182,983-80,080
12/16/2009 1:12:04 PMRatio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2,4082,7332,960-75,243
12/16/2009 1:12:23 PMRatio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2,1392,5603,214-73,613
12/16/2009 1:12:42 PMRatio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec1,7322,6313,402-70,385
12/16/2009 1:13:01 PMRatio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2,3512,7373,060-67,158
12/16/2009 1:13:20 PMRatio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec2,4572,7152,888-64,984
12/16/2009 1:13:39 PMRatio of Page Lookups/sec to Batch Requests/sec < 100 to 1.\\DB04\SQLServer:Buffer Manager\Page lookups/sec75,77890,860105,942493,887
Back to the top

SQLServer:Buffer Manager Page reads/sec

Description: Number of physical database page reads issued. Number of physical database page reads issued. 80 – 90 per second is normal, anything that is above indicates indexing or memory constraint.

\SQLServer:Buffer Manager\Page reads/sec

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\SQLServer:Buffer Manager\Page reads/sec04807,50923,584652405433476
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
12/16/2009 1:06:41 PMPage Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec01272572,506
12/16/2009 1:07:00 PMPage Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec22474914,754
12/16/2009 1:07:19 PMPage Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec2462472484,283
12/16/2009 1:07:38 PMPage Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec1242884954,612
12/16/2009 1:07:57 PMPage Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec4946187439,435
12/16/2009 1:08:16 PMPage Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec6036136188,638
12/16/2009 1:08:35 PMPage Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec6166176188,066
12/16/2009 1:08:54 PMPage Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec5215876207,153
12/16/2009 1:09:13 PMPage Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec4966197437,088
12/16/2009 1:09:32 PMPage Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec4935557395,955
12/16/2009 1:09:51 PMPage Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec4946187406,290
12/16/2009 1:10:10 PMPage Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec4965896205,666
12/16/2009 1:10:29 PMPage Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec4965797435,288
12/16/2009 1:10:48 PMPage Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec4946187435,386
12/16/2009 1:11:07 PMPage Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec4955887424,888
12/16/2009 1:11:26 PMPage Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec4935566194,411
12/16/2009 1:11:45 PMPage Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec4945887434,481
12/16/2009 1:12:04 PMPage Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec4965787434,227
12/16/2009 1:12:23 PMPage Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec4945846204,104
12/16/2009 1:12:42 PMPage Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec3725577443,766
12/16/2009 1:13:01 PMPage Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec4956197444,051
12/16/2009 1:13:20 PMPage Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec0121364657
12/16/2009 1:13:39 PMPage Reads/sec > 90\\DB04\SQLServer:Buffer Manager\Page reads/sec13,7557,50923,584
Back to the top

SQLServer:Buffer Manager Page writes/sec

Description: Number of physical database page writes issued. 80 – 90 per second is normal, anything above, check the lazy writer/sec and Checkpoint pages/sec counter, if these counters are relatively high then, this indicates a memory constraint.

\SQLServer:Buffer Manager\Page writes/sec

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\SQLServer:Buffer Manager\Page writes/sec085471926211
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
12/16/2009 1:04:28 PMPage Writes/sec > 90\\DB04\SQLServer:Buffer Manager\Page writes/sec013754725,893
Back to the top

SQLServer:General Statistics


SQLServer:General Statistics Logins/sec

Description: Total number of logins started per second. Greater than 2 per second may indicate that applications are not correctly using connection pooling.

\SQLServer:General Statistics\Logins/sec

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\SQLServer:General Statistics\Logins/sec002-3000-
Back to the top

SQLServer:General Statistics Logouts/sec

Description: Total number of logouts started per second. Greater than 2 per second indicates that the application is not correctly using connection pooling.

\SQLServer:General Statistics\Logouts/sec

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\SQLServer:General Statistics\Logouts/sec002-200--
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
*OK\\DB04\SQLServer:General Statistics\Logouts/sec002-2
Back to the top

SQLServer:General Statistics User Connections

Description: Number of users connected to the system. The number of users currently connected to the SQL Server.

\SQLServer:General Statistics\User Connections

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\SQLServer:General Statistics\User Connections111821604192021
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
12/16/2009 1:04:28 PMPossible disparity between User Connections and Batch Requests per second\\DB04\SQLServer:General Statistics\User Connections11121247.3684210526316
12/16/2009 1:04:47 PMPossible disparity between User Connections and Batch Requests per second\\DB04\SQLServer:General Statistics\User Connections111111-47.3684210526316
12/16/2009 1:05:44 PMPossible disparity between User Connections and Batch Requests per second\\DB04\SQLServer:General Statistics\User Connections111111-18.9473684210526
Back to the top

SQLServer:Latches


SQLServer:Latches Latch Waits/sec

Description: Number of latch requests that could not be granted immediately and had to wait before being granted. In other words, these are the amount of latches, in a one second period that had to wait.

\SQLServer:Latches\Latch Waits/sec

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\SQLServer:Latches\Latch Waits/sec067.1052,010.0487,025.623204.40327.9976.961.695
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
12/16/2009 1:04:09 PMLatch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec0.3979.63526.2020
12/16/2009 1:04:28 PMLatch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec25.53860.73110.799,681.208
12/16/2009 1:04:47 PMLatch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec2.7841.72177.9233,039.707
12/16/2009 1:06:03 PMLatch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec00.4991.198-288.514
12/16/2009 1:06:41 PMLatch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec7.181206.715348.0544,667.668
12/16/2009 1:07:00 PMLatch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec175.544227.277288.6784,581.939
12/16/2009 1:07:19 PMLatch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec175.184229.149307.8884,159.201
12/16/2009 1:07:38 PMLatch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec13.127152.942238.862,468.446
12/16/2009 1:07:57 PMLatch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec0.3961.7413.19-124.642
12/16/2009 1:08:16 PMLatch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec00.9432.385-126.682
12/16/2009 1:08:35 PMLatch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec0.5941.7853.369-106.25
12/16/2009 1:08:54 PMLatch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec0.5971.7363.173-99.785
12/16/2009 1:09:13 PMLatch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec0.5961.2612.59-99.167
12/16/2009 1:09:32 PMLatch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec1.1881.6862.575-88.597
12/16/2009 1:09:51 PMLatch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec0.7971.4892.382-85.748
12/16/2009 1:10:10 PMLatch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec0.1991.1942.188-84.178
12/16/2009 1:10:29 PMLatch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec0.3981.3932.785-78.085
12/16/2009 1:10:48 PMLatch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec0.9921.7362.583-71.27
12/16/2009 1:11:07 PMLatch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec1.1951.9892.583-65.853
12/16/2009 1:11:26 PMLatch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec0.5961.2392.572-69.169
12/16/2009 1:11:45 PMLatch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec0.5951.893.381-61.148
12/16/2009 1:12:04 PMLatch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec0.9941.6582.587-60.456
12/16/2009 1:12:23 PMLatch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec0.5961.6382.388-58.279
12/16/2009 1:12:42 PMLatch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec0.5971.8393.585-54.709
12/16/2009 1:13:01 PMLatch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec0.3981.8882.982-52.423
12/16/2009 1:13:20 PMLatch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec0.3980.7971.595-57.743
12/16/2009 1:13:39 PMLatch Wait Times are greater than 10 milliseconds on average\\DB04\SQLServer:Latches\Latch Waits/sec234.0031,122.0252,010.0487,025.623
Back to the top

SQLServer:Latches\Total Latch Wait Time Total Latch Wait Time (ms)

Description: Total latch wait time (milliseconds) for latch requests that had to wait in the last second.

\SQLServer:Latches\Total Latch Wait Time (ms)

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\SQLServer:Latches\Total Latch Wait Time (ms)038012,32542,6121,2321412417
Back to the top

SQLServer:Memory Manager


SQLServer:Memory Manager Memory Grants Pending

Description: Current number of processes waiting for a workspace memory grant. Memory Grants Pending records the number of connections that are waiting for memory before they can begin processing a memory intensive query such as a sort or hash operation. Connections that wait in this state for a long enough time will eventually get an 8645 error (A time out occurred while waiting for memory resources to execute the query. Rerun the query). A spid waiting in this state will have a waittype of 0x0040 (RESOURCE_SEMAPHORE) in sysprocesses. If this counter remains above zero for any significant amount of time then you will need to track down what queries are doing sorts/hashes and run them through Index Tuning Wizard to see if they can get a more efficient plan.

\SQLServer:Memory Manager\Memory Grants Pending

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\SQLServer:Memory Manager\Memory Grants Pending0-000---
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
*OK\\DB04\SQLServer:Memory Manager\Memory Grants Pending0-00
Back to the top

SQLServer:Memory Manager Total Server Memory (KB)

Description: Total amount of dynamic memory the server is currently consuming

\SQLServer:Memory Manager\Total Server Memory (KB)

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\SQLServer:Memory Manager\Total Server Memory (KB)1,208,0721,230,2061,257,472-164,31215,0751,231,5301,233,3691,235,586
Back to the top

SQLServer:SQL Statistics


SQLServer:SQL Statistics Batch Requests/sec

Description: Number of SQL batch requests received by server. This counter measures the number of batch requests that SQL Server receives per second, and generally follows in step to how busy your server's CPUs are. Generally speaking, over 1000 batch requests per second indicates a very busy SQL Server, and could mean that if you are not already experiencing a CPU bottleneck, that you may very well soon. Of course, this is a relative number, and the bigger your hardware, the more batch requests per second SQL Server can handle. From a network bottleneck approach, a typical 100Mbs network card is only able to handle about 3000 batch requests per second. If you have a server that is this busy, you may need to have two or more network cards, or go to a 1Gbs network card. Note: Sometimes low batch requests/sec can be misleading. If there were a SQL statements/sec counter, this would be a more accurate measure of the amount of SQL Server activity. For example, an application may call only a few stored procedures yet each stored procedure does lot of work. In that case, we will see a low number for batch requests/sec but each stored procedure (one batch) will execute many SQL statements that drive CPU and other resources. As a result, many counter thresholds based on the number of batch requests/sec will seem to identify issues because the batch requests on such a server are unusually low for the level of activity on the server. We cannot conclude that a SQL Server is not active simply by looking at only batch requests/sec. Rather, you have to do more investigation before deciding there is no load on the server. If the average number of batch requests/sec is below 5 and other counters (such as SQL Server processor utilization) confirm the absence of significant activity, then there is not enough of a load to make any recommendations or identify issues regarding scalability.

\SQLServer:SQL Statistics\Batch Requests/sec

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\SQLServer:SQL Statistics\Batch Requests/sec029382111
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
*OK\\DB04\SQLServer:SQL Statistics\Batch Requests/sec02938
Back to the top

SQLServer:SQL Statistics SQL Compilations/sec

Description: Number of SQL compilations.

\SQLServer:SQL Statistics\SQL Compilations/sec

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec0418663444
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
12/16/2009 1:04:09 PMA ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec0120
12/16/2009 1:04:28 PMA ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec245505
12/16/2009 1:04:47 PMA ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec2613477
12/16/2009 1:05:06 PMA ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec001-38
12/16/2009 1:05:25 PMA ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec001-26
12/16/2009 1:05:44 PMA ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec01517
12/16/2009 1:06:03 PMA ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec001-19
12/16/2009 1:06:22 PMA ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec001-18
12/16/2009 1:06:41 PMA ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec81118237
12/16/2009 1:07:00 PMA ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec4814138
12/16/2009 1:07:19 PMA ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec51015175
12/16/2009 1:07:38 PMA ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec371197
12/16/2009 1:07:57 PMA ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec051061
12/16/2009 1:08:16 PMA ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec03627
12/16/2009 1:08:35 PMA ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec05954
12/16/2009 1:08:54 PMA ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec051049
12/16/2009 1:09:13 PMA ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec031028
12/16/2009 1:09:32 PMA ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec051043
12/16/2009 1:09:51 PMA ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec14927
12/16/2009 1:10:10 PMA ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec041033
12/16/2009 1:10:29 PMA ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec071052
12/16/2009 1:10:48 PMA ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec03916
12/16/2009 1:11:07 PMA ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec15934
12/16/2009 1:11:26 PMA ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec051133
12/16/2009 1:11:45 PMA ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec03914
12/16/2009 1:12:04 PMA ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec16941
12/16/2009 1:12:23 PMA ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec031013
12/16/2009 1:12:42 PMA ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec051128
12/16/2009 1:13:01 PMA ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec15927
12/16/2009 1:13:20 PMA ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec14918
12/16/2009 1:13:39 PMA ratio of more than 1 SQL Compilation for every 100 Batch Requests per second\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec6111666
Back to the top

SQLServer:SQL Statistics SQL Re-Compilations/sec

Description: Number of SQL re-compiles. This needs to be 0 as much as possible. A recompile can cause deadlocks and compile locks that are not compatible with any locking type.

\SQLServer:SQL Statistics\SQL Re-Compilations/sec

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec00100000
Back to the top

Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.
TimeConditionCounterMinAvgMaxHourly Trend
12/16/2009 1:04:28 PMA ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations\\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec00169
12/16/2009 1:08:16 PMA ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations\\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec0012
12/16/2009 1:08:35 PMA ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations\\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec0013
12/16/2009 1:09:51 PMA ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations\\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec0012
12/16/2009 1:10:48 PMA ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations\\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec0011
12/16/2009 1:11:07 PMA ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations\\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec0012
12/16/2009 1:11:45 PMA ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations\\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec0011
12/16/2009 1:12:04 PMA ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations\\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec0012
12/16/2009 1:13:01 PMA ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations\\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec0012
12/16/2009 1:13:20 PMA ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations\\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec0011
Back to the top

SQLServer:Locks


SQLServer:Locks Lock Requests/sec

Description: Number of new locks and lock conversions requested from the lock manager.

\SQLServer:Locks(_Total)\Lock Requests/sec

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\SQLServer:Locks(_Total)\Lock Requests/sec01,64823,448-7,5714,251591545523
Back to the top

SQLServer:Locks Lock Waits/sec

Description: Number of lock requests that could not be satisfied immediately and required the caller to wait before being granted the lock.

\SQLServer:Locks(_Total)\Lock Waits/sec

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\SQLServer:Locks(_Total)\Lock Waits/sec00260---
Back to the top

SQLServer:Locks Lock Wait Time (ms)

Description: Total wait time (milliseconds) for locks in the last second.

\SQLServer:Locks(_Total)\Lock Wait Time (ms)

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\SQLServer:Locks(_Total)\Lock Wait Time (ms)07,890489,1881,544,80443,216---
Back to the top

SQLServer:Locks Number of Deadlocks/sec

Description: Number of lock requests that resulted in a deadlock.

\SQLServer:Locks(_Total)\Number of Deadlocks/sec

Back to the top

Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.
NameMinAvgMaxHourly TrendStd Deviation90th Percentile80th Percentile70th Percentile
\\DB04\SQLServer:Locks(_Total)\Number of Deadlocks/sec0-000---
Back to the top


Disclaimer: This report was generated using the Performance Analysis of Logs (PAL) tool. The information provided in this report is provided "as is" and is intended for information purposes only. The authors and contributors of this tool take no responsibility for damages or losses incurred by use of this tool.